From: Pavel Machek <pavel@suse.cz>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: mingo@elte.hu, nickpiggin@yahoo.com.au, ak@suse.de,
linux-kernel@vger.kernel.org, rohit.seth@intel.com,
asit.k.mallick@intel.com
Subject: Re: [Patch] sched: new sched domain for representing multi-core
Date: Sun, 29 Jan 2006 17:56:47 +0100 [thread overview]
Message-ID: <20060129165645.GF1764@elf.ucw.cz> (raw)
In-Reply-To: <20060126015132.A8521@unix-os.sc.intel.com>
On Čt 26-01-06 01:51:33, Siddha, Suresh B wrote:
> Appended patch adds a new sched domain for representing multi-core with
> shared caches between cores. Consider a dual package system, each package
> containing two cores and with last level cache shared between cores with in a
> package. If there are two runnable processes, with this appended patch
> those two processes will be scheduled on different packages.
>
> On such system, with this patch we have observed 8% perf improvement with
> specJBB(2 warehouse) benchmark and 35% improvement with CFP2000 rate(with
> 2 users).
>
> This new domain will come into play only on multi-core systems with shared
> caches. On other systems, this sched domain will be removed by
> domain degeneration code. This new domain can be also used for implementing
> power savings policy (see OLS 2005 CMP kernel scheduler paper for more
> details.. I will post another patch for power savings policy soon)
Could we all do it with single CONFIG_SCHED_SMT or CONFIG_NUMA or
something like that? No need for zillion options...
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-29 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 9:51 [Patch] sched: new sched domain for representing multi-core Siddha, Suresh B
2006-01-27 0:08 ` Ingo Molnar
2006-01-27 3:51 ` Siddha, Suresh B
2006-01-28 0:00 ` Andrew Morton
2006-01-31 1:28 ` Siddha, Suresh B
2006-02-01 1:12 ` Andrew Morton
2006-02-01 1:48 ` Siddha, Suresh B
2006-02-01 2:21 ` Andrew Morton
2006-02-01 2:52 ` Siddha, Suresh B
2006-01-27 4:42 ` Andi Kleen
2006-01-28 1:45 ` Siddha, Suresh B
2006-01-29 16:56 ` Pavel Machek [this message]
2006-01-31 1:31 ` Siddha, Suresh B
2006-02-09 9:59 Samuel Thibault
2006-02-11 0:51 ` 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=20060129165645.GF1764@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=asit.k.mallick@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=rohit.seth@intel.com \
--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 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).