From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
lenb@kernel.org, menage@google.com
Subject: Re: [PATCH]cpuset: add new API to change cpuset top group's cpus
Date: Tue, 19 May 2009 14:01:18 +0200 [thread overview]
Message-ID: <1242734478.26820.502.camel@twins> (raw)
In-Reply-To: <8763fxpc1u.fsf@basil.nowhere.org>
On Tue, 2009-05-19 at 13:27 +0200, Andi Kleen wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
> >
> > Furthermore, I object to being able to remove online cpus from the top
> > cpuset, that just doesn't make sense.
>
> Note you can already do it at boot time with isolated_cpus=...
> So your objection seems to be a few years too late.
>
> Shaohua's patch just makes it work at runtime too.
No it doesn't. And isolcpus should die.
next prev parent reply other threads:[~2009-05-19 12:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 7:39 [PATCH]cpuset: add new API to change cpuset top group's cpus Shaohua Li
2009-05-19 8:40 ` Peter Zijlstra
2009-05-19 8:48 ` Shaohua Li
2009-05-19 8:56 ` Peter Zijlstra
2009-05-19 9:06 ` Shaohua Li
2009-05-19 9:31 ` Peter Zijlstra
2009-05-19 10:38 ` Peter Zijlstra
2009-05-19 13:37 ` Vaidyanathan Srinivasan
2009-05-28 2:34 ` Len Brown
2009-05-28 7:44 ` Vaidyanathan Srinivasan
2009-05-19 19:01 ` Len Brown
2009-05-19 22:36 ` Peter Zijlstra
2009-05-20 11:58 ` Andi Kleen
2009-05-20 12:17 ` Peter Zijlstra
2009-05-20 13:13 ` Andi Kleen
2009-05-20 13:41 ` Peter Zijlstra
2009-05-20 14:45 ` Andi Kleen
2009-05-20 17:36 ` Vaidyanathan Srinivasan
2009-05-21 1:22 ` Shaohua Li
2009-05-21 3:20 ` Vaidyanathan Srinivasan
2009-05-20 17:21 ` Vaidyanathan Srinivasan
2009-05-19 11:27 ` Andi Kleen
2009-05-19 12:01 ` Peter Zijlstra [this message]
2009-05-19 19:55 ` Paul Menage
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=1242734478.26820.502.camel@twins \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=shaohua.li@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