From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Mala Anand <manand@us.ibm.com>, Erich Focht <efocht@hpce.nec.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: Tue, 29 Jul 2003 07:29:07 -0700 [thread overview]
Message-ID: <3850000.1059488946@[10.10.2.4]> (raw)
In-Reply-To: <OF607D10C6.EC89E09C-ON87256D72.004CBCAE@us.ibm.com>
>>> If you want data supporting my assumptions: Ted Ts'o's talk at OLS
>>> shows the necessity to rebalance ASAP (even in try_to_wake_up).
>
>> If this is the patch I am thinking of, it was the (attached) one I sent
> them,
>> which did a light "push" rebalance at try_to_wake_up. Calling
> load_balance
>> at try_to_wake_up seems very heavy-weight. This patch only looks for an
> idle
>> cpu (within the same node) to wake up on before task activation, only if
> the
>> task_rq(p)->nr_running is too long. So, yes, I do believe this can be
>> important, but I think it's only called for when we have an idle cpu.
>
> The patch that you sent to Rajan didn't yield any improvement on
> specjappserver so we did not include that in the ols paper. What
> is described in the ols paper is "calling load-balance" from
> try-to-wake-up. Both calling load-balance from try-to-wakeup and
> the "light push" rebalance at try_to_wake_up are already done in
> Andrea's 0(1) scheduler patch.
Are the balances you're doing on wakeup global or node-local?
M.
next prev parent reply other threads:[~2003-07-29 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 14:06 [Lse-tech] Re: [patch] scheduler fix for 1cpu/node case Mala Anand
2003-07-29 14:29 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 20:49 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-30 16:34 Luck, Tony
2003-07-29 16:04 Mala Anand
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='3850000.1059488946@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ak@muc.de \
--cc=efocht@hpce.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=manand@us.ibm.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).