From: ccmail111 <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: cgroup tasks file error
Date: Wed, 15 Dec 2010 14:08:21 -0800 (PST) [thread overview]
Message-ID: <116655.19981.qm@web34207.mail.mud.yahoo.com> (raw)
In-Reply-To: <20101215175158.GB9587-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
--- On Wed, 12/15/10, Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> wrote:
> From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> Subject: Re: cgroup tasks file error
> To: "ccmail111" <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Date: Wednesday, December 15, 2010, 12:51 PM
> * ccmail111 <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> [2010-12-14 10:22:32]:
>
> >
> >
> > --- On Tue, 12/14/10, Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> wrote:
> >
> > > From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> > > Subject: Re: cgroup tasks file error
> > > To: "ccmail111" <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> > > Cc: "Jue Hong" <honshj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
> containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> > > Date: Tuesday, December 14, 2010, 12:41 PM
> > > On Tue, Dec 14, 2010 at 11:03 PM,
> > > ccmail111 <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> > > wrote:
> > > >
> > > > Isn't ns mounted by default ?
> > > > I rebooted machine,
> > > > based on 2.6.32 kernel.
> > > >
> > > > Then,
> > > >
> > > > [host:~]$ mkdir /dev/cgroup
> > > > [host:~]$ mount -t cgroup cpuset
> -ocpuset,ns
> > > /dev/cgroup
> > > > [host:~]$ ps aux | grep libvirt
> > > > root 575 0.6 0.9 88816 2216
> ?
> > > Sl 17:28 0:00 myproc --daemon
> > > > root 654 0.0 0.2 4044 664
> ttyS0
> > > S+ 17:29 0:00 grep libvirt
> > > > [host:~]$ mkdir /dev/cgroup/hello
> > > > [host:~]$ cat /dev/cgroup/hello/tasks
> > > > [host:~]$ echo 0 >
> /dev/cgroup/hello/cpuset.cpus
> > > > [host:~]$ echo 0 >
> /dev/cgroup/hello/cpuset.mems
> > >
> > > Can you paste the output of
> > >
> > > cat /dev/cgroup/hello/cpuset.cpus and mems.
> > >
> > > Also please paste the o/p of
> /dev/cgroup/cpuset.cpus and
> > > mems
> > >
> > > > [host:~]$ echo 575 >
> /dev/cgroup/hello/tasks
> > > > [host:~]$ cat /dev/cgroup/hello/tasks
> > > > 575
> > > > [host:~]$ id
> > > > uid=0(root) gid=0(root) groups=0(root)
> > > > [host:~]$
> > > >
> > > > Now, I try to move the task out - the
> parent/root:
> > > >
> > > > [host:~]$ echo 575 > /dev/cgroup/tasks
> > > > -bash: echo: write error: Operation not
> permitted
> > >
> > > can you send us the o/p of
> > >
> > > ls -al /dev/cgroup
> > >
> > > and ls -al /dev/cgroup/hello
> > >
> > > Balbir
> > >
> > ----
> >
> > Please find output requested below:
> >
> >
> > [host:~]$ mkdir /dev/cgroup/hello
> > [host:~]$ cat /dev/cgroup/hello/tasks
> > [host:~]$ echo 0 > /dev/cgroup/hello/cpuset.cpus
> > [host:~]$ echo 0 > /dev/cgroup/hello/cpuset.mems
> > [host:~]$ echo 575 > /dev/cgroup/hello/tasks
> > [host:~]$ cat /dev/cgroup/hello/tasks
> > 575
> > [host:~]$ id
> > uid=0(root) gid=0(root) groups=0(root)
> > [host:~]$ echo 575 > /dev/cgroup/tasks
> > -bash: echo: write error: Operation not permitted
> > [host:~]$ cat /dev/cgroup/hello/cpuset.cpus
> > 0
> > [host:~]$ cat /dev/cgroup/hello/cpuset.mems
> > 0
> > [host:~]$ cat /dev/cgroup/cpuset.mems
> > 0
> > [host:~]$ cat /dev/cgroup/cpuset.cpus
> > 0
> > [host:~]$ ls -al /dev/cgroup/
> > total 0
> > drwxr-xr-x 3 root root 0 Dec 14
> 17:29 .
> > drwxr-xr-x 11 root root 2980 Dec 14 17:29 ..
> > -r--r--r-- 1 root root 0 Dec 14
> 17:29 cgroup.procs
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.cpu_exclusive
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.cpus
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.mem_exclusive
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.mem_hardwall
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.memory_migrate
> > -r--r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.memory_pressure
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.memory_pressure_enabled
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.memory_spread_page
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.memory_spread_slab
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.mems
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.sched_load_balance
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 cpuset.sched_relax_domain_level
> > drwxr-xr-x 2 root root 0 Dec 14
> 17:29 hello
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 notify_on_release
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:29 release_agent
> > -rw-r--r-- 1 root root 0 Dec 14
> 17:31 tasks
> > [host:~]$ ls -al /dev/cgroup/hello/
> > total 0
> > drwxr-xr-x 2 root root 0 Dec 14 17:29 .
> > drwxr-xr-x 3 root root 0 Dec 14 17:29 ..
> > -r--r--r-- 1 root root 0 Dec 14 17:29 cgroup.procs
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.cpu_exclusive
> > -rw-r--r-- 1 root root 0 Dec 14 17:30 cpuset.cpus
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.mem_exclusive
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.mem_hardwall
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.memory_migrate
> > -r--r--r-- 1 root root 0 Dec 14 17:29
> cpuset.memory_pressure
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.memory_spread_page
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.memory_spread_slab
> > -rw-r--r-- 1 root root 0 Dec 14 17:30 cpuset.mems
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.sched_load_balance
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> cpuset.sched_relax_domain_level
> > -rw-r--r-- 1 root root 0 Dec 14 17:29
> notify_on_release
> > -rw-r--r-- 1 root root 0 Dec 14 17:30 tasks
> > [host:~]$ id
> > uid=0(root) gid=0(root) groups=0(root)
> > [host:~]$
> >
>
> Looks like Serge's ns suggestion solved your problem,
> right?
>
> --
> Three Cheers,
> Balbir
>
Yes, Balbir, thats right.
IMHO, it would nice if it can be documented on wiki or such.
Thanks everyone for suggestions..
next prev parent reply other threads:[~2010-12-15 22:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 22:25 cgroup tasks file error ccmail111
[not found] ` <149701.57773.qm-VjZBGxy5l2evuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-13 23:16 ` Serge E. Hallyn
[not found] ` <20101213231628.GA8624-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2010-12-14 1:02 ` Matt Helsley
[not found] ` <20101214010243.GC26523-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-12-14 7:28 ` ccmail111
[not found] ` <464217.68381.qm-VjZBGxy5l2evuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-14 9:39 ` Jue Hong
[not found] ` <AANLkTi=tpq0Jo9WAd5eu=fP2bLaSG6iLpHtAVR1xe=Ub-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-14 17:33 ` ccmail111
[not found] ` <166364.22607.qm-VjZBGxy5l2evuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-14 17:40 ` Serge Hallyn
2010-12-14 19:23 ` ccmail111
2010-12-14 17:41 ` Balbir Singh
[not found] ` <AANLkTi=gR2JVXf0uidRMZo7s88th1wu-4+AbC0ZwRUJk-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-14 18:22 ` ccmail111
[not found] ` <478906.58374.qm-NvXQCeNhX6ivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-15 17:51 ` Balbir Singh
[not found] ` <20101215175158.GB9587-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2010-12-15 22:08 ` ccmail111 [this message]
2010-12-14 1:23 ` ccmail111
-- strict thread matches above, loose matches on Subject: below --
2010-12-14 1:27 ccmail111
[not found] ` <478892.90636.qm-m6GApcO8MwWvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-14 1:34 ` Li Zefan
[not found] ` <4D06C996.9010101-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2010-12-14 2:50 ` ccmail111
[not found] ` <903526.98695.qm-I5qWG7eNxUOvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-14 17:13 ` Serge E. Hallyn
2010-12-14 9:31 ` Greg Kurz
[not found] ` <4D07398D.9050002-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2010-12-14 17:17 ` ccmail111
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=116655.19981.qm@web34207.mail.mud.yahoo.com \
--to=ccmail111-/e1597as9lqavxtiumwx3w@public.gmane.org \
--cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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.