From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
menage@google.com, containers@lists.linux-foundation.org
Subject: Re: Question for remount
Date: Mon, 23 Feb 2009 10:56:04 +0800 [thread overview]
Message-ID: <49A21044.40402@cn.fujitsu.com> (raw)
In-Reply-To: <49A20976.2050301@cn.fujitsu.com>
Li Zefan wrote:
>> 1. Documentation/cgroups/cgroup.txt says
>> #mount -oremount,cpuset,ns /dev/cgroup
>> But this should be
>> #mount -tcgroup none /dev/cgroup -oremount,cpuset,ns
>>
>
> I agree. Actually I noticed this long ago.
>
> Doing this won't remove cpuacct from the cgroup hierarchy:
> # mount -t cgroup -o cpu,cpuacct xxx /mnt
> # mount -o remount,cpu /mnt
> This will get you right:
> # mount [-t cgroup] -o remount,cpu xxx /mnt
>
How about this patch:
[PATCH] cgroups: fix documentation about remount
This won't remove cpuacct from the mounted hierachy:
# mount -t cgroup -o cpu,cpuacct xxx /mnt
# mount -o remount,cpu /mnt
Because for this usage mount(8) will append the new options to the current
options.
And this will get you right:
# mount [-t cgroup] -o remount,cpu xxx /mnt
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
---
Documentation/cgroups/cgroups.txt | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/Documentation/cgroups/cgroups.txt b/Documentation/cgroups/cgroups.txt
index 93feb84..5cbeab2 100644
--- a/Documentation/cgroups/cgroups.txt
+++ b/Documentation/cgroups/cgroups.txt
@@ -337,8 +337,13 @@ subsystems, type:
To change the set of subsystems bound to a mounted hierarchy, just
remount with different options:
+# mount -o remount,cpuset,ns hier1 /dev/cgroup
-# mount -o remount,cpuset,ns /dev/cgroup
+Now numtasks is removed from the hierarchy and ns is added.
+
+Note this will add ns to the hierarchy but won't remove numtasks or
+cpuset:
+# mount -o remount,ns /dev/cgroup
Note that changing the set of subsystems is currently only supported
when the hierarchy consists of a single (root) cgroup. Supporting
--
1.5.4.rc3
next prev parent reply other threads:[~2009-02-23 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 10:02 Question for remount KAMEZAWA Hiroyuki
2009-02-20 16:22 ` Paul Menage
2009-02-21 0:45 ` KAMEZAWA Hiroyuki
2009-02-23 2:32 ` Li Zefan
2009-02-23 23:57 ` KAMEZAWA Hiroyuki
2009-02-24 1:33 ` Li Zefan
2009-02-23 2:27 ` Li Zefan
2009-02-23 2:56 ` Li Zefan [this message]
2009-02-24 1:36 ` KAMEZAWA Hiroyuki
2009-02-24 1:41 ` Li Zefan
2009-02-24 1:47 ` KAMEZAWA Hiroyuki
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=49A21044.40402@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.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