From: hawkes@sgi.com
To: Dinakar Guniguntala <dino@in.ibm.com>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
linux-ia64@vger.kernel.org, hawkes@sgi.com,
Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] 2.6.13-mm1: cpuset + build_sched_domains() fix
Date: Fri, 02 Sep 2005 20:11:14 +0000 [thread overview]
Message-ID: <20050902201114.16681.88184.sendpatchset@jackhammer.engr.sgi.com> (raw)
Ingo, Dino, and Andrew,
Here is the "cpuset + build_sched_domains() mangles structures" set of
patches against 2.6.13-mm1.
Patch #3: Re-enable "dynamic sched domains" by backing out the hack
introduced last week.
Signed-off-by: John Hawkes <hawkes@sgi.com>
Index: linux/kernel/cpuset.c
=================================--- linux.orig/kernel/cpuset.c 2005-08-28 16:41:01.000000000 -0700
+++ linux/kernel/cpuset.c 2005-09-02 11:18:43.000000000 -0700
@@ -628,13 +628,6 @@
* lock_cpu_hotplug()/unlock_cpu_hotplug() pair.
*/
-/*
- * Hack to avoid 2.6.13 partial node dynamic sched domain bug.
- * Disable letting 'cpu_exclusive' cpusets define dynamic sched
- * domains, until the sched domain can handle partial nodes.
- * Remove this #if hackery when sched domains fixed.
- */
-#if 0
static void update_cpu_domains(struct cpuset *cur)
{
struct cpuset *c, *par = cur->parent;
@@ -675,11 +668,6 @@
partition_sched_domains(&pspan, &cspan);
unlock_cpu_hotplug();
}
-#else
-static void update_cpu_domains(struct cpuset *cur)
-{
-}
-#endif
static int update_cpumask(struct cpuset *cs, char *buf)
{
reply other threads:[~2005-09-02 20:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050902201114.16681.88184.sendpatchset@jackhammer.engr.sgi.com \
--to=hawkes@sgi.com \
--cc=akpm@osdl.org \
--cc=dino@in.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.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