From: "Chris Friesen" <cfriesen@nortel.com>
To: rparedes@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP Affinity and nice
Date: Wed, 23 Aug 2006 14:54:50 -0600 [thread overview]
Message-ID: <44ECC09A.7090909@nortel.com> (raw)
In-Reply-To: <38798.127.0.0.1.1156346673.squirrel@forexproject.com>
Rich Paredes wrote:
> So since cpumax5 has a lower nice value and thus a higher priority (25 in
> this case), shouldn't it be given it's own cpu. If I give cpumax5 a nice
> value of -20, it does start using it's own cpu.
>
> My explanation would be that since the scheduler tries to limit cpu
> affinity, the nice value of 0 isn't enough to get the scheduler to move
> this process to another processors run queue. I could be totally wrong
> here though.
I think you are correct. The load balancer doesn't think that this is
enough of an imbalance to go through the effort of swapping two
processes around.
Chris
next prev parent reply other threads:[~2006-08-23 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 15:24 SMP Affinity and nice Rich Paredes
2006-08-23 15:36 ` Jan Engelhardt
2006-08-24 1:30 ` Peter Williams
[not found] ` <3bfa83ed0608231920h5d9ef2bbxee71badedb38e3f7@mail.gmail.com>
2006-08-24 4:39 ` Peter Williams
2006-08-23 20:54 ` Chris Friesen [this message]
2006-08-24 5:24 ` Peter Williams
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=44ECC09A.7090909@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rparedes@gmail.com \
/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