From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
linux-kernel@vger.kernel.org, pj@sgi.com, menage@google.com,
vegard.nossum@gmail.com, Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [PATCH] cpuset: Rework sched domains and CPU hotplug handling
Date: Tue, 29 Jul 2008 08:40:54 +0200 [thread overview]
Message-ID: <1217313654.18049.59.camel@twins> (raw)
In-Reply-To: <20080728140748.GB18144@elte.hu>
On Mon, 2008-07-28 at 16:07 +0200, Ingo Molnar wrote:
> * Max Krasnyansky <maxk@qualcomm.com> wrote:
>
> > Max Krasnyansky wrote:
> > > This is an updated version of my previous cpuset patch:
> > > "Make rebuild_sched_domains() usable from any context (take 2)"
> >
> > Folks,
> >
> > Any comments on this patch ? We need this to complete sched domain
> > handling fixes/improvements that we started with the cpu_active_map,
> > and to avoid circular locking issues in the cpu hotplug ->
> > rebuild_sched_domains path.
>
> Paul, Peter, any comments?
I'm really not that at home with all that cgroup fiddling, so I'd like a
word from the two Pauls..
Questions I have at the moment:
- do we really need a new workqueue for this? Can't we use the regular
keventd stuff, now that Oleg fixed the get_online_cpus() thing?
(3da1c84c00c7e5fa8348336bd8c342f9128b0f14)
- aren't there funny races with the async_rebuild_sched_domains()
stuff?
next prev parent reply other threads:[~2008-07-29 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 22:33 [PATCH] cpuset: Rework sched domains and CPU hotplug handling Max Krasnyansky
2008-07-26 19:40 ` Max Krasnyansky
2008-07-28 14:07 ` Ingo Molnar
2008-07-29 6:40 ` Peter Zijlstra [this message]
2008-07-29 16:59 ` Max Krasnyansky
2008-07-31 20:14 ` Paul Jackson
2008-08-01 1:58 ` Max Krasnyansky
2008-08-01 6:49 ` Max Krasnyansky
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=1217313654.18049.59.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=pj@sgi.com \
--cc=vegard.nossum@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.