search for: runq

...784k free, 1636920k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ GROUP COMMAND 19256 PREUSSAG 25 0 14804 8168 3520 R 99.9 0.1 116:00.06 PREUSSAG smbd This is a really big file server: agestt71:~ # ps -ef | grep smbd |wc -l 1014 here's an sar -A: 10:15:01 runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 10:18:01 2 1262 2.17 2.16 1.82 10:21:01 1 1264 2.08 2.16 1.87 10:24:01 1 1269 2.09 2.18 1.93 10:27:01 1 1262 2.20 2.14 1.95 10:30:01...

...q without updating any scores */ extraq_add_sort_update(d, EXTRA_UTIL_Q, 0); } @@ -265,8 +228,6 @@ static inline void __del_from_queue(stru { struct list_head *list = LIST(d); ASSERT(__task_on_queue(d)); - PRINT(3,"Removing domain %i.%i (bop= %"PRIu64") from runq/waitq\n", - d->domain->domain_id, d->vcpu_id, PERIOD_BEGIN(EDOM_INFO(d))); list_del(list); list->next = NULL; ASSERT(!__task_on_queue(d)); @@ -279,13 +240,12 @@ static inline void list_insert_sort( { struct list_head *cur; - /* Iterate through...

Hi, I am looking to measure how long a thread takes to migrate between cpu''s and how often , what I have is below which is checking just one process is this the correct track to be on here? My aim is to look at a process and look at upping the reboose_interval on some of our servers. #!/usr/sbin/dtrace -s sched:::off-cpu { self->cpu = cpu; self->timestamp=timestamp; }

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,

...it_default_yield); +static int __read_mostly sched_credit_tslice_ms = CSCHED_DEFAULT_TSLICE_MS; +integer_param("sched_credit_tslice_ms", sched_credit_tslice_ms); /* * Physical CPU @@ -176,6 +172,9 @@ struct csched_private { uint32_t credit; int credit_balance; uint32_t runq_sort; + /* Period of master and tick in milliseconds */ + unsigned tslice_ms, tick_period_us, ticks_per_tslice; + unsigned credits_per_tslice; }; static void csched_tick(void *_cpu); @@ -326,7 +325,7 @@ csched_free_pdata(const struct scheduler spin_lock_irqsave(&prv->lock...

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

...41 AM sdc 209.10 26764.99 0.00 128.00 0.41 1.94 0.60 12.57 10:10:41 AM sdc1 209.10 26764.99 0.00 128.00 0.41 1.94 0.60 12.57 10:10:41 AM md0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 10:09:41 AM runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 10:10:41 AM 0 167 1.02 1.03 1.00 Thanks in advance..... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100927/c651de7b/attachment.ht...

...ell r910 with rhel6.2 on it and libvirt 0.8. This machine is hosting 12 virtual guests. Every 3 - 5 months the server crashes for no apparent reason. The logs show no kernel panics or other issues causing the crash. The sar logs show a very high context switch count ( approx. 170000). and also high runq-sz (approx. 10 - 18). The cpu's were mostly idle, memory usage low, no swapping, disk io very low as well. This also occurs on a number of other rhel6.2 servers I have using KVM/libvirt/qemu for virtualization. I am curious if anyone else has reported incidents like this. After the crash the se...

...0.00 99.85 11:32:46 AM all 0.05 0.00 0.05 0.00 99.90 11:32:51 AM all 0.00 0.00 0.05 0.00 99.95 Average: all 0.04 0.00 0.06 0.01 99.89 %sar -q 5 5 Linux 2.6.9-42.ELsmp 05/08/2007 11:32:58 AM runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 11:33:03 AM 1 112 3.02 3.02 3.00 11:33:08 AM 1 112 3.02 3.02 3.00 11:33:13 AM 1 112 3.01 3.02 3.00 11:33:18 AM 1 112 3.01 3.02 3.00 11:33:23...

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

...quest my supplier to replace the cards with working ones. I think their driver is at fault because I found a message in /var/adm/message saying "WARNING: arcmsr duplicate scsi_hba_pkt_comp(9F) on same scsi_pkt(9S)" and immediately after that " WARNING: kstat rcnt == 0 when exiting runq, please check". Then the system was hung. The comments in the code introducing these changes tell us that drivers behaving this way could panic the system (or at least that how I understood these comments). I''ve reached my limits here. If anyone has ideas on how to determine what&...

...I propose the patch to fix the problem. it is just removing BUG_ON(!vcpu_running) I use this method because consider the following circum stances. a)SEDF, BVT scheduler is not checked on this (CREDIT scheduler should use same policy) b)We have some possibility to change the vcpu state within runq. (vcpu_running => !vcpu_running) c)This function is scheduler main route. so we want to avoid using the lock. This proposal assumes pausecnt policy is loosely locked. 2)Implement Strict Lock Policy in scheduler Implement v->pausecnt policy within the lock of schedule_data[cpu].s...

Hi all, This is my first post to the list, I hope someone out there can help! I am running xen 3.0.3, with CentOS 5.2 based Dom0 (kernel-xen-2.6.18-92.1.22.el5) Recently I have noticed some complete system lockups on a few different servers. Neither Dom0 or any of the guests respond to pings, connecting a keyboard and monitor to the system only shows a blank screen. Nothing is written to logs

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

...0 0 0000204 [SLPQ syncer 0xffffffff805609c0][SLP] syncer 30 ffffff007b65c9c0 0 0 0 0000204 [SLPQ vlruwt 0xffffff007b65c9c0][SLP] vnlru 29 ffffff007b5dd000 0 0 0 0000204 [SLPQ psleep 0xffffffff8056a4b8][SLP] bufdaemon 28 ffffff007b5dd340 0 0 0 000020c [RUNQ] pagezero 27 ffffff007b5dd680 0 0 0 0000204 [SLPQ psleep 0xffffffff8057116c][SLP] vmdaemon 26 ffffff007b90c680 0 0 0 0000204 [SLPQ psleep 0xffffffff8057111c][SLP] pagedaemon 25 ffffff007b90c9c0 0 0 0 0000204 [IWAIT] swi0: sio 24 ffffff007b95e000 0...

...ed.ipiwakeup.requested: 1033 kern.sched.ipiwakeup.delivered: 1033 kern.sched.ipiwakeup.usemask: 1 kern.sched.ipiwakeup.useloop: 0 kern.sched.ipiwakeup.onecpu: 0 kern.sched.ipiwakeup.htt2: 0 kern.sched.followon: 0 kern.sched.pfollowons: 0 kern.sched.kgfollowons: 0 kern.sched.preemption: 1 kern.sched.runq_fuzz: 1 kern.ccpu: 1948 kern.devstat.numdevs: 8 kern.devstat.generation: 313 kern.devstat.version: 6 kern.kobj_methodcount: 132 kern.log_wakeups_per_second: 5 kern.log_console_output: 1 kern.always_console_output: 0 kern.msgbuf: kern.msgbuf_clear: 0 kern.smp.maxcpus: 16 kern.smp.active: 1 kern.smp...