From: Ingo Molnar <mingo@elte.hu>
To: Ken Chen <kenchen@google.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched: fix sd_parent_degenerate on non-numa smp machine
Date: Mon, 8 Dec 2008 13:53:19 +0100 [thread overview]
Message-ID: <20081208125319.GD16560@elte.hu> (raw)
In-Reply-To: <b040c32a0812071847x351c0315pb2cdb59150a59e79@mail.gmail.com>
* Ken Chen <kenchen@google.com> wrote:
> The addition of SD_SERIALIZE flag added to SD_NODE_INIT prevented top level
> dummy numa sched_domain to be properly degenerated on non-numa smp machine.
> The reason is that in sd_parent_degenerate(), it found that the child and
> parent does not have comon sched_domain flags due to SD_SERIALIZE. However,
> for non-numa smp box, the top level is a dummy with a single sched_group.
>
> Filter out SD_SERIALIZE if it is on non-numa machine to properly degenerate
> top level node sched_domain. this will cut back some of the sd domain walk
> in the load balancer code.
>
> Signed-off-by: Ken Chen <kenchen@google.com>
applied to tip/sched/core, thanks Ken!
Ingo
prev parent reply other threads:[~2008-12-08 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 2:47 Ken Chen
2008-12-08 12:53 ` Ingo Molnar [this message]
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=20081208125319.GD16560@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=kenchen@google.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
Powered by JetHome