All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: npiggin@suse.de, linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [patch] sched: introduce SD_BALANCE_FORK for ht/mc/smp domains
Date: Fri, 27 Jul 2007 00:18:30 +0200	[thread overview]
Message-ID: <20070726221830.GA4113@elte.hu> (raw)
In-Reply-To: <20070726183225.GJ3318@linux-os.sc.intel.com>


* Siddha, Suresh B <suresh.b.siddha@intel.com> wrote:

> Introduce SD_BALANCE_FORK for HT/MC/SMP domains.
> 
> For HT/MC, as caches are shared, SD_BALANCE_FORK is the right thing to 
> do. Given that NUMA domain already has this flag and the scheduler 
> currently doesn't have the concept of running threads belonging to a 
> process as close as possible(i.e., forking may keep close, but 
> periodic balance later will likely take them far away), introduce 
> SD_BALANCE_FORK for SMP domain too.
> 
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>

i'm not opposed to this fundamentally, but it would be nice to better 
map the effects of this change: do you have any particular workload 
under which you've tested this and under which you've seen it makes a 
difference? I'd expect this to improve fork-intense half-idle workloads 
perhaps - things like a make -j3 on a 4-core CPU.

	Ingo

  reply	other threads:[~2007-07-26 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 18:32 [patch] sched: introduce SD_BALANCE_FORK for ht/mc/smp domains Siddha, Suresh B
2007-07-26 22:18 ` Ingo Molnar [this message]
2007-07-26 22:34   ` Siddha, Suresh B
2007-07-27  1:22     ` Nick Piggin
2007-07-27 19:09       ` Siddha, Suresh B
2007-07-29 21:16     ` Ingo Molnar
2007-07-30 17:53       ` Siddha, Suresh B

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=20070726221830.GA4113@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --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.