From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, Martin Bligh <mbligh@google.com>,
Paul Menage <menage@google.com>,
Simon.Derr@bull.net, linux-kernel@vger.kernel.org,
Dinakar Guniguntala <dino@in.ibm.com>,
Rohit Seth <rohitseth@google.com>, Robin Holt <holt@sgi.com>,
dipankar@in.ibm.com, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: [RFC] cpuset: add interface to isolated cpus
Date: Thu, 19 Oct 2006 20:17:14 +1000 [thread overview]
Message-ID: <453750AA.1050803@yahoo.com.au> (raw)
In-Reply-To: <20061019092607.17547.68979.sendpatchset@sam.engr.sgi.com>
Paul Jackson wrote:
> From: Paul Jackson <pj@sgi.com>
>
> Enable user code to isolate CPUs on a system from the domains that
> determine scheduler load balancing.
>
> This is already doable using the boot parameter "isolcpus=". The folks
> running realtime code on production systems, where some nodes are
> isolated for realtime, and some not, and where it is unacceptable
> to reboot to adjust this, need to be able to change which CPUs are
> isolated from the scheduler balancing code on the fly.
>
> This is done by exposing the kernels cpu_isolated_map as a cpumask
> in the root cpuset directory, in a file called 'isolated_cpus',
> where it can be read and written by sufficiently privileged user code.
This should be done outside cpusets.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-10-19 10:17 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 [this message]
2006-10-19 17:55 ` Paul Jackson
2006-10-19 18:07 ` Nick Piggin
2006-10-19 18:56 ` Paul Jackson
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=453750AA.1050803@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--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=pj@sgi.com \
--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