Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

repost - RFC [Patch] Remove "please try 'cgroup_disable=memory' option if you don't want memory cgroups" printk at boot time.

32 views
Skip to first unread message

Larry Woodman

unread,
Apr 20, 2010, 10:30:02 AM4/20/10
to
Re-posting, cc'ing linux-mm as requested:

We are considering removing this printk at boot time from RHEL because
it will confuse customers, encourage them to change the boot parameters
and generate extraneous support calls. Its documented in
Documentation/kernel-parameters.txt anyway. Any thoughts???

Larry Woodman


rhel6-cgroup.patch

KAMEZAWA Hiroyuki

unread,
Apr 20, 2010, 8:30:01 PM4/20/10
to

For RHEL, I agree removing the message makes sense.
But I'm unsure that small machine users, who never use memcg, can notice some
amount of memory are eaten at boot time.

Many distro tends to enable memcg by default and consume memory.

printk(KERN_INFO "allocated %ld bytes of page_cgroup\n", total_usage);
- printk(KERN_INFO "please try 'cgroup_disable=memory' option if you"
- " don't want memory cgroups\n");

Hmm.

printk(KERN_INFO "If you don't want page_cgroup,
you can disable this by boot option, cgroup_disable=memory".)

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.

Bye,
-Kame

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Li Zefan

unread,
Apr 20, 2010, 9:00:03 PM4/20/10
to
> 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.

KAMEZAWA Hiroyuki

unread,
Apr 20, 2010, 9:10:01 PM4/20/10
to
On Wed, 21 Apr 2010 08:56:20 +0800
Li Zefan <li...@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

0 new messages