From: Suresh Jayaraman <sjayaraman@suse.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: High priority threads causing severe CPU load imbalances
Date: Tue, 06 Apr 2010 18:42:45 +0530 [thread overview]
Message-ID: <4BBB334D.5040308@suse.de> (raw)
I have a simple test program that accepts number of threads(pthreads) to
be created as a input. Each of these threads that gets created invokes a
function which is just a infinite while loop. The main function after
creating those threads goes in a infinite loop itself
My test machine is a Dual Core AMD Opteron(tm) 860 with 8
sockets(non-HT), I run this test program with number of threads ==
number of CPUs:
./loadcpu -t 16
I see 100% CPU utilization on almost all CPUs (via mpstat/htop/vmstat).
When the above threads are running, if I introduce a few high priority
threads by doing:
nice -n -13 ./loadcpu -t 3
After a short while, I see a few CPUs becoming idle at ~0% utilization
(the number of CPUs becoming idle equals roughly the number of high
priority threads i.e. 3). When I stop the high priority threads, the CPU
utilization comes back to normal i.e. ~100%.
This is reproducible on 2.6.32.10 stable kernel with all the recent all
SMT fixes (I hope) and I think it would be reproducible in current
upstream as well.
sched_mc_power_savings has been always set to 0.
I spent a while staring at the load balancing and the thread migration
code, but could not figure out why this is happening. Would appreciate
any pointers.
Thanks,
--
Suresh Jayaraman
next reply other threads:[~2010-04-06 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 13:12 Suresh Jayaraman [this message]
2010-04-06 14:08 ` High priority threads causing severe CPU load imbalances Peter Zijlstra
2010-04-06 16:35 ` Suresh Jayaraman
2010-04-08 16:15 ` Peter Zijlstra
2010-04-09 2:20 ` Masayuki Igawa
2010-04-07 4:42 ` Andy Lutomirski
2010-04-07 7:44 ` Peter Zijlstra
2010-04-07 5:46 ` Masayuki Igawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BBB334D.5040308@suse.de \
--to=sjayaraman@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.