From: Zefan Li <lizefan@huawei.com>
To: Serge Hallyn <serge.hallyn@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, tj@kernel.org,
"Stéphane Graber" <stgraber@ubuntu.com>,
christianvanbrauner@gmail.com
Subject: Re: cpusets in non-unified hierarchy broken?
Date: Fri, 13 Feb 2015 10:16:32 +0800 [thread overview]
Message-ID: <54DD5E80.4090402@huawei.com> (raw)
In-Reply-To: <20150212214950.GB10662@ubuntumail>
On 2015/2/13 5:49, Serge Hallyn wrote:
> Hi,
>
> as of some point in 3.18, cpuset.cpus doesn't seem to be
> enforced any more. I don't see an obvious reason in the
> code, but it seems likely to be related to the effective_cpus.
>
> If I mount -t cgroup -o cpuset cpuset /mnt and then mkdir /mnt/lxc,
> then /mnt/lxc has:
>
> ====================================================
> ubuntu@cpuset1:~$ cat /mnt/lxc/cpuset.effective_cpus
>
> ubuntu@cpuset1:~$ cat /mnt/lxc/cpuset.cpus
> 0-3
This happens when you enable cgroup.clone_children.
Thanks for reporting this bug! Will fix it soon.
prev parent reply other threads:[~2015-02-13 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:49 cpusets in non-unified hierarchy broken? Serge Hallyn
2015-02-13 2:16 ` Zefan Li [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=54DD5E80.4090402@huawei.com \
--to=lizefan@huawei.com \
--cc=christianvanbrauner@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@ubuntu.com \
--cc=stgraber@ubuntu.com \
--cc=tj@kernel.org \
/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