public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Simon Derr <simon.derr@bull.net>
Cc: simon.derr@bull.net, linux-kernel@vger.kernel.org
Subject: Re: [rfc][patch] 1/2 Additional cpuset features
Date: Sat, 11 Sep 2004 01:08:08 -0700	[thread overview]
Message-ID: <20040911010808.2b283c9a.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409101036090.2891@daphne.frec.bull.fr>

Good luck with these patches, Simon, though I do not support them.

For the record, I was the one most responsible for removing these two
patches:

 1) auto task migration on cpuset change, and
 2) cpuset relative CPU/Memory numbering.

I continue to think that these can be done just as well in user space. 
A bit better in user space actually, as the locking for (1) is easier
from user space, and the opportunity for more flexible adaption to
different renumbering needs that (2) attempts is easier from user space.

But if others find these worth persuing in kernel space, so be it.

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

  reply	other threads:[~2004-09-11  8:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  8:52 [rfc][patch] 1/2 Additional cpuset features Simon Derr
2004-09-11  8:08 ` Paul Jackson [this message]
2004-09-23 19:43   ` Christoph Lameter
2004-09-23 23:41     ` Paul Jackson
2004-09-24  0:06       ` Christoph Lameter
2004-09-24  1:13         ` Paul Jackson
2004-09-24  1:17         ` Anton Blanchard
2004-09-24 14:41           ` Robin Holt
2004-09-24 16:07             ` 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=20040911010808.2b283c9a.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon.derr@bull.net \
    /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