public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: linux-kernel@vger.kernel.org
Cc: Henning Fehrmann <henning.fehrmann@aei.mpg.de>
Subject: Idle core on overloaded CPU?
Date: Thu, 23 Oct 2008 14:12:32 +0200	[thread overview]
Message-ID: <49006A30.7030208@aei.mpg.de> (raw)

Hi,

on Intel X3220 CPU based systems (4 physical cores) I came across the
following thing (Debian etch, with vanilla kernel 2.6.25.9):

starting the following:
$ screen -d -m stress -c 2
$ nice -19 screen -d -m stress -c 4

This causes two cores to be 100% busy in user state and one core to be
busy in 100% nice state. However, the remaining core is idle. Even
watching it over longer stretches of time, the situation remains static.

I guess it's a kernel misconfiguration on my part (config available here:
https://n0.aei.uni-hannover.de/linux/kernel/config-2.6.25.9-nodes
), but if not could this be a scheduling bug?

Thanks for any hint

Cheers

Carsten

                 reply	other threads:[~2008-10-23 12:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49006A30.7030208@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=henning.fehrmann@aei.mpg.de \
    --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