From: "Luck, Tony" <tony.luck@intel.com>
To: "Andrew Theurer" <habanero@us.ibm.com>,
"Erich Focht" <efocht@hpce.nec.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"LSE" <lse-tech@lists.sourceforge.net>
Cc: "Andi Kleen" <ak@muc.de>, <torvalds@osdl.org>
Subject: RE: [Lse-tech] Re: [patch] scheduler fix for 1cpu/node case
Date: Wed, 30 Jul 2003 09:34:51 -0700 [thread overview]
Message-ID: <DD755978BA8283409FB0087C39132BD101B0100B@fmsmsx404.fm.intel.com> (raw)
> As for idle balances, we may be able to go a step further:
> follow the range rules, but do a more aggressive/frequent search.
Be cautious about how much work you do here ... while you can burn
as much cpu time as you like on an idle cpu without affecting anything,
you need to be sure that your activities don't burn too much bus
bandwidth, or cause cache lines to ping-pong around the machine. The
classic case of this has been seen while one cpu is trying to boot,
and the other 31 idle cpus beat the bus to death looking to see
whether they can "help".
-Tony
next reply other threads:[~2003-07-30 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 16:34 Luck, Tony [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 20:49 [patch] scheduler fix for 1cpu/node case Bill Davidsen
2003-08-22 15:46 ` [Lse-tech] " Andrew Theurer
2003-08-22 22:56 ` Nick Piggin
2003-08-23 0:12 ` Andrew Theurer
2003-08-23 0:29 ` Nick Piggin
2003-08-23 0:47 ` William Lee Irwin III
2003-08-23 8:48 ` Nick Piggin
2003-08-23 14:32 ` Andrew Theurer
2003-08-23 1:31 ` Martin J. Bligh
2003-07-29 16:04 Mala Anand
2003-07-29 14:06 Mala Anand
2003-07-29 14:29 ` Martin J. Bligh
2003-07-28 19:16 Erich Focht
2003-07-29 2:24 ` Andrew Theurer
2003-07-29 10:08 ` Erich Focht
2003-07-29 13:33 ` [Lse-tech] " Andrew Theurer
2003-07-30 15:23 ` Erich Focht
2003-07-30 15:44 ` Andrew Theurer
2003-07-31 21:45 ` Erich Focht
2003-08-01 0:26 ` Martin J. Bligh
2003-08-01 16:30 ` [Lse-tech] " Erich Focht
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=DD755978BA8283409FB0087C39132BD101B0100B@fmsmsx404.fm.intel.com \
--to=tony.luck@intel.com \
--cc=ak@muc.de \
--cc=efocht@hpce.nec.com \
--cc=habanero@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).