public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Lynch <jason@calindora.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG?,FEATURE?] One core idles with 4 nice and 1 regular process
Date: Tue, 16 Jun 2009 19:09:59 +0000 (UTC)	[thread overview]
Message-ID: <h18qm7$bf$1@ger.gmane.org> (raw)

First, a description of the problem, and a fairly simple way to test it:

All of this is running on my quad-core Q6600. First, I start four nice -n 
19 processes, each of which does nothing but busy-wait. (In my case, I 
used a simple python script, but any CPU-bound process will do.) At this 
point, top shows all four cores being utilized, at approximately 100% 
nice each.

At this point, I start another of these busy-waiting processes, except 
with no nice adjustment, so it runs at regular priority. After doing so, 
top now reports the following CPU usage: one core is 100% user, two cores 
are 100% nice, and finally, one last core is 100% idle, doing nothing, 
despite a total of five processes being available to run.

I thought I first noticed this running a 2.6.29 kernel, and thought about 
bisecting, but my test 2.6.28 kernel also exhibited the behavior. I 
couldn't test any previous kernels due to a lack of ext4 support. Both my 
current 2.6.30 kernel and the torvalds/linux-2.6.git HEAD also show the 
behavior.

Now, I'm not sure if this is a bug or a strange feature (though it seems 
very bug-like to me) or perhaps a configuration problem, but I'd like to 
find out nonetheless.

If I can provide any additional information to help, I'll be happy to 
oblige.


             reply	other threads:[~2009-06-16 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 19:09 Jason Lynch [this message]
2009-06-18  1:02 ` [BUG?,FEATURE?] One core idles with 4 nice and 1 regular process Jason Lynch

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='h18qm7$bf$1@ger.gmane.org' \
    --to=jason@calindora.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox