search for: runqueues

Hi, This patch intends to accurate vcpu weighting for CPU intensive job. The reason of this problem is that vcpu round-robin queue blocks large weight vcpus by small weight vcpus. For example, we assume following case on 2pcpu environment. (with 4domains (each domain has 2vcpus)) dom1 vcpu0,1 w128 credit 4 dom2 vcpu0,1 w128 credit 4 dom3 vcpu0,1 w256 credit 8 dom4 vcpu0,1 w512 credit 15

I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler

Address some credit2 issues. This patch series, along with the recent changes to the cpupools interface, should address some of the strange credit2 instability. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This patch implements cpu offline feature. Best Regards Haitao Shan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi gang! At work I have a DL320 G2 machine I use as my desktop (I know, weird!...). Back when I ran RHEL WS 2.1 on it, it always ran a SMP kernel because it has a HypterThread capable processor. When I installed (fresh from scratch) Centos 4.4 on it a while back, though, Centos installed only the UP kernel. I've looked in the BIOS for settings to enable/disable HT support and I don't

While investigating erratic performance on one our our servers, I'm getting some very odd performance stats coming from vmstat. What initially appeared to be happening is the machine goes into a hard loop in some mod_perl webserver code. Now there still may be an issue with the code, but my code examinations show no possible way this could be happening, but what I'm writing to you

...better power saving ability with negligible performance impact, following areas may be tweaked and listed here for comments first. Goal is not to silly save power with sacrifice of performance, e.g. we don''t want to prevent migration when there''re free cpus with some pending runqueues. But when free computing power is more than existing requirement, power aware policy can be pushed to choose a less power-intrusive decision. Of course even in latter case, it''s controllable with a scheduler parameter like csched_private.power and exposed to user. ---- a) when there&...

Hi, I am trying to understand Hypervisor_sched_op function and I have few question regarding this - 1. I understand that a guest VM can use the above function with "yield", in order to relinquish CPU time to other guests with running tasks. a) So when the guest VM makes this call does it save/persist any scheduling information about its current processes like runqueue, process state -

Hi, I am trying to understand Hypervisor_sched_op function and I have few question regarding this - 1. I understand that a guest VM can use the above function with "yield", in order to relinquish CPU time to other guests with running tasks. a) So when the guest VM makes this call does it save/persist any scheduling information about its current processes like runqueue, process state -

As discussed in a previous e-mail, this patch series implements yield for the credit scheduler. This allows a VM to actually yield (give up the cpu to another VM) when it wants to. This has been shown to be effective when used in the spinlock code to avoid wasting time spinning when another vcpu is not currently scheduled. _______________________________________________ Xen-devel mailing list

In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> credit2: Fix erronous ASSERT In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. v2: - Update comment

I am seeing a problem with Dom0 crashing on x86_64 whenever I create a DomU. I''ve done some more testing, and it appears that this problem is somehow related to networking. Dom0 crashes as soon as the networking services are started when DomU is coming up. As an experiment, I brought up DomU without networking, and it stayed up. As soon as I started DomU with networking enabled, however,

After updating a very old x86_64 3.x install to 3.8 it still has kernel-2.4.21-27.0.2.EL. Then if I repeat the yum update command, it offers to install kernel 2.4.21-47.EL.ia32e. Neither of these situations seems quite right. -- Les Mikesell lesmikesell at gmail.com

I am currently looking at a bug report[1] which is happening when a Xen PVM guest with multiple VCPUs is running a high IO database load (a test script is available in the bug report). In experimenting it seems that this happens (or is getting more likely) when the number of VCPUs is 8 or higher (though I have not tried 6, only 2 and 4), having autogroup enabled seems to make it more likely, too

Hello all, We are working on a new project idea for xen platform. I have summarized as well as given detailed description of what we are trying to achieve. I request your comments on the feasibility of this project. Also I have pointed some relevant works which I feel is primitive considering the goal we are trying to achieve. I request to point me to relevant links if there are any other works

I'm afraid that I am at a loss here. I am new to Asterisk, and have successfully set up SIP. But I cannot get my FXS card working, and I'm not sure what else I can try. # modprobe wcfxo /lib/modules/2.4.21-37.0.1.ELsmp/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may

Instead of storing the map per CPU provide and use per task storage. That prepares for local kmaps which are preemptible. The context switch code is preparatory and not yet in use because kmap_atomic() runs with preemption disabled. Will be made usable in the next step. The context switch logic is safe even when an interrupt happens after clearing or before restoring the kmaps. The kmap index in

sched_sedf.c used o have its own mechanism for producing tracing-alike kind of information (domain block, wakeup, etc.). Nowadays, with an even not so high number of pCPUs/vCPUs, just trying to enable this makes the serial console completely unusable, produces tons of very hard to parse and interpreet logging and can easily livelock Dom0. Moreover, pretty much the same result this is struggling to

Hi all, I am having confusion regarding the way a newly created domain is allocated vcpu. Initially during dom0 creation alloc_vcpu is called to create vcpu structs for all the available cpu''s and assigned to dom0. But its not the case for domU creation. 1. So how will dom0 relinquish/share vcpu to/with a newly created domU. Does this happen as part of the shared_info page mapping??

..._run_job_work(struct work_struct *w) * drm_sched_init - Init a gpu scheduler instance * * @sched: scheduler instance - * @ops: backend operations for this scheduler - * @submit_wq: workqueue to use for submission. If NULL, an ordered wq is - * allocated and used - * @num_rqs: number of runqueues, one for each priority, up to DRM_SCHED_PRIORITY_COUNT - * @credit_limit: the number of credits this scheduler can hold from all jobs - * @hang_limit: number of times to allow a job to hang before dropping it - * @timeout: timeout value in jiffies for the scheduler - * @timeout_wq: workqueue to use...