From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Larry Woodman <lwoodman@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: repost - RFC [Patch] Remove "please try 'cgroup_disable=memory' option if you don't want memory cgroups" printk at boot time.
Date: Wed, 21 Apr 2010 09:59:35 +0900 [thread overview]
Message-ID: <20100421095935.54109d78.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <4BCE4D34.5050200@cn.fujitsu.com>
On Wed, 21 Apr 2010 08:56:20 +0800
Li Zefan <lizf@cn.fujitsu.com> wrote:
> > My biggest concern is that we don't have man(5) cgroup as other file systems.
> > If we have man(5), the best place for this kind of information will be it.
> > I think most of users will never see kernel-parameter.txt ..
> >
> > If usual distros are shipped with man(5) cgroup, I agree removing
> > this in upstream.
> > (We have man pages for libcgroup but not man(5) for cgroup file system.)
> >
> > I'm sorry if I don't notice that the latest man package has cgroup section.
> >
>
> We have a man-page for cpuset, which was written by Paul Jackson,
> the author of cpuset.
>
But there is no description about "cpuset can be mounted as cgroup".
Maybe there are no updates for 2 years even if it exists.
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-04-21 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 14:26 Larry Woodman
2010-04-21 0:25 ` KAMEZAWA Hiroyuki
2010-04-21 0:56 ` Li Zefan
2010-04-21 0:59 ` KAMEZAWA Hiroyuki [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=20100421095935.54109d78.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=lwoodman@redhat.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