From: Paul Jackson <pj@sgi.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, menage@google.com,
a.p.zijlstra@chello.nl, vegard.nossum@gmail.com,
lizf@cn.fujitsu.com
Subject: Re: [PATCH] cpuset: Rework sched domains and CPU hotplug handling (2.6.27-rc1)
Date: Mon, 4 Aug 2008 22:56:36 -0500 [thread overview]
Message-ID: <20080804225636.541527e8.pj@sgi.com> (raw)
In-Reply-To: <48977E81.4040207@qualcomm.com>
Max wrote:
> Actually it is appropriate, and there is one more user of the
> arch_reinit_sched_domains() which is S390 topology updates.
> Those things (mc_power and topology updates) have to update domain flags based
> on the mc/smt power and current topology settings.
Hmmm ... ok I suppose.
Could we have the kernel/sched.c code, in this case, call the
kernel/cpuset.c routine async_rebuild_sched_domains(), rather
than the synchronous rebuild_sched_domains() call (in your naming)
which required details of the get_online_cpus() and put_online_cpus()
wrapping to leak into kernel/sched.c:arch_reinit_sched_domains()
routine?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-08-05 3:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 22:59 [PATCH] cpuset: Rework sched domains and CPU hotplug handling (2.6.27-rc1) Max Krasnyansky
2008-08-02 11:39 ` Paul Jackson
2008-08-02 16:32 ` Max Krasnyansky
2008-08-03 3:51 ` Paul Jackson
2008-08-03 18:07 ` Max Krasnyansky
2008-08-04 6:00 ` Paul Jackson
2008-08-04 22:11 ` Max Krasnyansky
2008-08-05 3:56 ` Paul Jackson [this message]
2008-08-05 20:30 ` Max Krasnyansky
2008-08-05 23:05 ` Paul Jackson
2008-08-06 3:24 ` Max Krasnyansky
2008-08-06 3:29 ` Paul Jackson
2008-08-06 3:53 ` Max Krasnyansky
2008-08-06 4:28 ` Paul Jackson
2008-08-06 5:03 ` Max Krasnyansky
2008-08-06 5:46 ` Paul Jackson
2008-08-06 20:20 ` Max Krasnyansky
2008-08-06 20:29 ` Paul Jackson
2008-08-06 20:30 ` Paul Menage
2008-08-06 20:56 ` Paul Jackson
2008-08-06 20:36 ` 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=20080804225636.541527e8.pj@sgi.com \
--to=pj@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=maxk@qualcomm.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--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.