From: Paul Jackson <pj@sgi.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: suresh.b.siddha@intel.com, dino@in.ibm.com, menage@google.com,
Simon.Derr@bull.net, linux-kernel@vger.kernel.org,
mbligh@google.com, rohitseth@google.com, dipankar@in.ibm.com
Subject: Re: [RFC] Cpuset: explicit dynamic sched domain control flags
Date: Thu, 19 Oct 2006 01:15:46 -0700 [thread overview]
Message-ID: <20061019011546.39c7a8df.pj@sgi.com> (raw)
In-Reply-To: <453732CF.7050801@yahoo.com.au>
> But please don't let *users* try to deal with it.
Agreed - that's why I am about to send a patch that removes
the sched domain side affects of the cpu_exclusive flag.
Well, not entirely agreed. User space code does need
to be able to specify some cpus as isolated from scheduler
balancing. I will send a second patch to support 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-10-19 8:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 23:03 [RFC] Cpuset: explicit dynamic sched domain control flags Paul Jackson
2006-10-17 18:43 ` Siddha, Suresh B
2006-10-17 19:18 ` Paul Jackson
2006-10-18 2:01 ` Siddha, Suresh B
2006-10-18 7:05 ` Paul Jackson
2006-10-18 17:50 ` Siddha, Suresh B
2006-10-19 6:30 ` Paul Jackson
2006-10-19 6:39 ` Nick Piggin
2006-10-19 7:03 ` Paul Jackson
2006-10-19 8:09 ` Nick Piggin
2006-10-19 8:15 ` Paul Jackson [this message]
2006-10-19 8:18 ` Paul Jackson
2006-10-18 17:49 ` Dinakar Guniguntala
2006-10-19 6:00 ` Paul Jackson
2006-10-19 6:28 ` 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=20061019011546.39c7a8df.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=dino@in.ibm.com \
--cc=dipankar@in.ibm.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