From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: mingo@elte.hu, npiggin@suse.de
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: [patch] sched: introduce SD_BALANCE_FORK for ht/mc/smp domains
Date: Thu, 26 Jul 2007 11:32:25 -0700 [thread overview]
Message-ID: <20070726183225.GJ3318@linux-os.sc.intel.com> (raw)
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>
---
diff --git a/include/linux/topology.h b/include/linux/topology.h
index d0890a7..dc15a9f 100644
--- a/include/linux/topology.h
+++ b/include/linux/topology.h
@@ -104,6 +104,7 @@
.flags = SD_LOAD_BALANCE \
| SD_BALANCE_NEWIDLE \
| SD_BALANCE_EXEC \
+ | SD_BALANCE_FORK \
| SD_WAKE_AFFINE \
| SD_WAKE_IDLE \
| SD_SHARE_CPUPOWER, \
@@ -135,6 +136,7 @@
.flags = SD_LOAD_BALANCE \
| SD_BALANCE_NEWIDLE \
| SD_BALANCE_EXEC \
+ | SD_BALANCE_FORK \
| SD_WAKE_AFFINE \
| SD_WAKE_IDLE \
| SD_SHARE_PKG_RESOURCES\
@@ -166,6 +168,7 @@
.flags = SD_LOAD_BALANCE \
| SD_BALANCE_NEWIDLE \
| SD_BALANCE_EXEC \
+ | SD_BALANCE_FORK \
| SD_WAKE_AFFINE \
| SD_WAKE_IDLE \
| BALANCE_FOR_PKG_POWER,\
next reply other threads:[~2007-07-26 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 18:32 Siddha, Suresh B [this message]
2007-07-26 22:18 ` [patch] sched: introduce SD_BALANCE_FORK for ht/mc/smp domains Ingo Molnar
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=20070726183225.GJ3318@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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