From: Paul Jackson <pj@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: akpm@osdl.org, 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, suresh.b.siddha@intel.com
Subject: Re: [RFC] cpuset: add interface to isolated cpus
Date: Thu, 19 Oct 2006 11:56:52 -0700 [thread overview]
Message-ID: <20061019115652.562054ca.pj@sgi.com> (raw)
In-Reply-To: <4537BEDA.8030005@yahoo.com.au>
> > So ... where should it be done?
>
> sched.c I suppose.
Are we discussing where the implementing code should go,
or where the isolated cpu map special file should be
exposed to user space?
And you didn't answer my other questions, such as:
1) If your other patch to manipulate sched domains
has code that belongs in kernel/cpuset.c, and
special files that belong in /dev/cpuset, why
shouldn't this one naturally go in the same places?
2) Why ... why? What would be better about sched.c
and what's wrong with where it is (the code and
the exposed file)?
--
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-10-19 18:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 9:26 [RFC] cpuset: add interface to isolated cpus Paul Jackson
2006-10-19 10:17 ` Nick Piggin
2006-10-19 17:55 ` Paul Jackson
2006-10-19 18:07 ` Nick Piggin
2006-10-19 18:56 ` Paul Jackson [this message]
2006-10-19 19:03 ` Nick Piggin
2006-10-20 3:37 ` Paul Jackson
2006-10-20 8:02 ` Nick Piggin
2006-10-20 14:52 ` Nick Piggin
2006-10-20 20:03 ` Paul Jackson
2006-10-20 19:59 ` Paul Jackson
2006-10-20 20:01 ` Paul Jackson
2006-10-20 20:59 ` Siddha, Suresh B
2006-10-21 1:33 ` Paul Jackson
2006-10-21 6:14 ` Nick Piggin
2006-10-21 7:24 ` Paul Jackson
2006-10-21 10:51 ` Nick Piggin
2006-10-22 4:54 ` Paul Jackson
2006-10-20 21:04 ` Dinakar Guniguntala
2006-10-23 3:18 ` Paul Jackson
2006-10-23 5:07 ` Nick Piggin
2006-10-23 5:51 ` Paul Jackson
2006-10-23 5:40 ` Siddha, Suresh B
2006-10-23 6:06 ` Paul Jackson
2006-10-23 6:07 ` Paul Jackson
2006-10-23 6:17 ` Nick Piggin
2006-10-23 6:41 ` Paul Jackson
2006-10-23 6:49 ` Nick Piggin
2006-10-23 6:48 ` Paul Jackson
2006-10-23 20:58 ` Paul Jackson
2006-10-23 19:50 ` Dinakar Guniguntala
2006-10-23 20:47 ` Paul Jackson
2006-10-24 15:44 ` Paul Jackson
2006-10-25 19:40 ` 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=20061019115652.562054ca.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--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