From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: mingo@elte.hu, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch] sched: remove unnecessary sched domains
Date: Sat, 02 Apr 2005 13:59:17 +1000 [thread overview]
Message-ID: <424E1895.2070409@yahoo.com.au> (raw)
In-Reply-To: <20050401193121.B5598@unix-os.sc.intel.com>
Siddha, Suresh B wrote:
> On Sat, Apr 02, 2005 at 12:07:27PM +1000, Nick Piggin wrote:
>
>>I was thinking we could fix that by running balance on fork/exec multiple
>>times from top to bottom level domains. I'll have to measure the cost of
>>doing that, because it may be worthwhile.
>
>
> Agreed.
>
> BTW, why are we setting SD_BALANCE_FORK flag for NUMA domain on i386, ia64.
> This should be set only on x86_64 and that too not for Intel systems.
>
Mainly to see whether anyone reports regressions, and to exercise
the code a bit.
--
SUSE Labs, Novell Inc.
prev parent reply other threads:[~2005-04-02 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 0:20 [Patch] sched: remove unnecessary sched domains Siddha, Suresh B
2005-04-02 2:07 ` Nick Piggin
2005-04-02 3:31 ` Siddha, Suresh B
2005-04-02 3:59 ` Nick Piggin [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=424E1895.2070409@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.