From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: pj@sgi.com, dino@in.ibm.com, menage@google.com
Cc: Simon.Derr@bull.net, linux-kernel@vger.kernel.org,
mbligh@google.com, rohitseth@google.com, dipankar@in.ibm.com,
nickpiggin@yahoo.com.au
Subject: exclusive cpusets broken with cpu hotplug
Date: Tue, 17 Oct 2006 19:25:48 -0700 [thread overview]
Message-ID: <20061017192547.B19901@unix-os.sc.intel.com> (raw)
When ever a cpu hotplug happens, current kernel calls build_sched_domains()
with cpu_online_map. That will destroy all the domain partitions(done by
partition_sched_domains()) setup so far by exclusive cpusets.
And its not just cpu hotplug, this happens even if someone changes multi core
sched power savings policy.
Anyone would like to fix it up? In the presence of cpusets, we basically
need to traverse all the exclusive sets and setup the sched domains
accordingly.
If no one does :( then I will do that when I get some time...
thanks,
suresh
next reply other threads:[~2006-10-18 2:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 2:25 Siddha, Suresh B [this message]
2006-10-18 7:14 ` exclusive cpusets broken with cpu hotplug Paul Jackson
2006-10-18 9:56 ` Robin Holt
2006-10-18 10:10 ` Paul Jackson
2006-10-18 10:53 ` Robin Holt
2006-10-18 21:07 ` Paul Jackson
2006-10-19 5:56 ` Paul Jackson
2006-10-18 12:16 ` Nick Piggin
2006-10-18 14:14 ` Siddha, Suresh B
2006-10-18 14:51 ` Nick Piggin
2006-10-19 6:15 ` Paul Jackson
2006-10-19 6:35 ` Nick Piggin
2006-10-19 6:57 ` Paul Jackson
2006-10-19 7:04 ` Nick Piggin
2006-10-19 7:33 ` Paul Jackson
2006-10-19 8:16 ` Nick Piggin
2006-10-19 8:31 ` Paul Jackson
2006-10-19 7:34 ` Paul Jackson
2006-10-19 8:07 ` Nick Piggin
2006-10-19 8:11 ` Paul Jackson
2006-10-19 8:22 ` Nick Piggin
2006-10-19 8:42 ` Paul Jackson
2006-10-18 17:54 ` Dinakar Guniguntala
2006-10-18 18:05 ` Paul Jackson
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=20061017192547.B19901@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=Simon.Derr@bull.net \
--cc=dino@in.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=rohitseth@google.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