All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: David Shwatrz <dshwatrz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cpuset filesystems - a (short) doubt
Date: Wed, 3 Apr 2013 11:52:45 +0800	[thread overview]
Message-ID: <515BA78D.6020405@huawei.com> (raw)
In-Reply-To: <CAJJAcocYoD2ZoUBXNa7jHMnhcwHBKNUKt5AKUUBkXH=-SRr5ZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 2013/4/2 22:17, David Shwatrz wrote:
> Hi,
> I have a question about cpuset filesystem - is it needed ?
> 
> In the cpuset example given in:
> http://lxr.free-electrons.com/source/Documentation/cgroups/cgroups.txt
> we do not use the cpuset filesystsm but the cgroup filesystsm.
> (mount -t cgroup -ocpuset cpuset /sys/fs/cgroup/cpuset)
> 
> On my distro, which uses systemd + cgroups:
> mount | grep "type cpuset"
> gives nothing.
> 
> On the other hands, mount | grep "type cgroup" | wc -l
> gives: 9
> 
> I looked in the code of other subsystems (like blk cgroup and  memcg -
> memory control groups) and there is no filesystsm in the code; see
> block/blk-cgroup.c
> mm/memcontrol.c
> 
> so is the cpuset filesystsm really needed ?
> 

The cpuset filesystem is for backward compatibility.

      parent reply	other threads:[~2013-04-03  3:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 14:17 cpuset filesystems - a (short) doubt David Shwatrz
     [not found] ` <CAJJAcocYoD2ZoUBXNa7jHMnhcwHBKNUKt5AKUUBkXH=-SRr5ZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-03  3:52   ` Li Zefan [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=515BA78D.6020405@huawei.com \
    --to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dshwatrz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.