From: Dinakar Guniguntala <dino@in.ibm.com>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: pj@sgi.com, menage@google.com, Simon.Derr@bull.net,
linux-kernel@vger.kernel.org, mbligh@google.com,
rohitseth@google.com, dipankar@in.ibm.com,
nickpiggin@yahoo.com.au
Subject: Re: exclusive cpusets broken with cpu hotplug
Date: Wed, 18 Oct 2006 23:24:58 +0530 [thread overview]
Message-ID: <20061018175458.GC7885@in.ibm.com> (raw)
In-Reply-To: <20061017192547.B19901@unix-os.sc.intel.com>
On Tue, Oct 17, 2006 at 07:25:48PM -0700, Siddha, Suresh B wrote:
> 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...
Suresh,
I have a patch (though a very old one...) for handling hotplug and cpusets.
However there were some ugly locking issues and nesting of locks that I
ran into and I never got the time to sort them out. Also there didnt
seem to be any users for it and so I had no motivation to further complicate
the cpusets code/sched domains code. However I can dust up the patches if
there is a need
-Dinakar
next prev parent reply other threads:[~2006-10-18 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 2:25 exclusive cpusets broken with cpu hotplug Siddha, Suresh B
2006-10-18 7:14 ` 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 [this message]
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=20061018175458.GC7885@in.ibm.com \
--to=dino@in.ibm.com \
--cc=Simon.Derr@bull.net \
--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 \
--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