From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: nickpiggin@yahoo.com.au, suresh.b.siddha@intel.com,
mbligh@google.com, menage@google.com, Simon.Derr@bull.net,
linux-kernel@vger.kernel.org, dino@in.ibm.com,
rohitseth@google.com, holt@sgi.com, dipankar@in.ibm.com,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [RFC] cpuset: remove sched domain hooks from cpusets
Date: Thu, 9 Nov 2006 02:59:28 -0800 [thread overview]
Message-ID: <20061109025928.cd51f505.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610230901470.27654@schroedinger.engr.sgi.com>
Andrew,
This patch is currently residing in your *-mm stack, as:
cpuset-remove-sched-domain-hooks-from-cpusets.patch
If it's easy for you to keep track of, I'd like to ask that you don't
push this to Linus until Dinakar and I (with the consent of various
mm experts) settle on the replacement mechanism for dealing with
sched domain partitioning (or whatever that turns in to.)
At the rate Dinakar and I are progressing, this likely means that this
"... remove ... hooks ..." patch will be sitting in *-mm through the
2.6.20 work, and go on to Linus for 2.6.21.
There are some folks actually depending on this mechanism, such as
some real time folks using this to inhibit load balancing on their
isolated CPUs. It would be polite not to yank out one mechanism
before its replacement is available.
If this sounds like a pain, or you'd just rather not baby sit this in
*-mm that long, then I'd have you drop the patch before I had you send
it to Linus without an accompanying replacement.
All else equal, I kind of like leaving this patch in *-mm for now, as
it puts a stake in the ground, indicating that the current connection
between the per-cpuset "cpu_exclusive" flag and sched domain partitions
is sitting on death row.
There seems to be a general concensus that death row is a good place for
that.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-11-09 10:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 9:23 [RFC] cpuset: remove sched domain hooks from cpusets Paul Jackson
2006-10-19 10:24 ` Nick Piggin
2006-10-19 19:03 ` Paul Jackson
2006-10-19 19:21 ` Nick Piggin
2006-10-19 19:50 ` Martin Bligh
2006-10-20 0:14 ` Paul Jackson
2006-10-20 16:03 ` Nick Piggin
2006-10-20 17:29 ` Siddha, Suresh B
2006-10-20 19:19 ` Paul Jackson
2006-10-20 19:00 ` Paul Jackson
2006-10-20 20:30 ` Dinakar Guniguntala
2006-10-20 21:41 ` Paul Jackson
2006-10-20 22:35 ` Dinakar Guniguntala
2006-10-20 23:14 ` Siddha, Suresh B
2006-10-21 5:37 ` Paul Jackson
2006-10-23 4:31 ` Siddha, Suresh B
2006-10-23 5:59 ` Paul Jackson
2006-10-21 23:05 ` Paul Jackson
2006-10-22 12:02 ` Paul Jackson
2006-10-23 3:09 ` Paul Jackson
2006-10-20 21:46 ` Paul Jackson
2006-10-21 18:23 ` Paul Menage
2006-10-21 20:55 ` Paul Jackson
2006-10-21 20:59 ` Paul Menage
2006-10-22 10:51 ` Paul Jackson
2006-10-23 5:26 ` Siddha, Suresh B
2006-10-23 5:54 ` Paul Jackson
2006-10-23 5:43 ` Siddha, Suresh B
2006-10-23 6:02 ` Nick Piggin
2006-10-23 6:16 ` Paul Jackson
2006-10-23 16:03 ` Christoph Lameter
2006-11-09 10:59 ` Paul Jackson [this message]
2006-10-23 16:01 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2006-10-30 21:26 [RFC] cpuset: Remove " Dinakar Guniguntala
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=20061109025928.cd51f505.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=dino@in.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--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