From: Paul Menage <menage@google.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Nikanth Karthikesan <knikanth@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: cpusets: document adding/removing cpus to cpuset elaborately
Date: Wed, 17 Jun 2009 02:42:58 -0700 [thread overview]
Message-ID: <6599ad830906170242v47b56368ra1b39ef2c5bb4a81@mail.gmail.com> (raw)
In-Reply-To: <4A383CAB.6060809@cn.fujitsu.com>
On Tue, Jun 16, 2009 at 5:45 PM, Li Zefan<lizf@cn.fujitsu.com> wrote:
> Nikanth Karthikesan wrote:
>> Writing a pid to the file, tasks adds that task to that cgroup/cpuset. But to
>> add a cpu/mem to a cpuset, the new list of cpus should be written to the
>> cpuset.mems file which would replace the old list of cpus. Make this clearer
>> in the documentation.
>>
>
> Though I think '>' already means overwrite so removing/adding cpus should
> always writing the full list of CPUs to 'cpus'
But in the context of cgroups/cpusets that's not always the case -
think of the "tasks" file.
>
> Acked-by: Li Zefan <lizf@cn.fujitsu.com>
Acked-by: Paul Menage <menage@google.com>
Paul
prev parent reply other threads:[~2009-06-17 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 11:16 Nikanth Karthikesan
2009-06-17 0:45 ` Li Zefan
2009-06-17 9:42 ` Paul Menage [this message]
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=6599ad830906170242v47b56368ra1b39ef2c5bb4a81@mail.gmail.com \
--to=menage@google.com \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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
all inboxes | Powered by JetHome®