All of lore.kernel.org
 help / color / mirror / Atom feed
From: ccmail111 <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: "Serge E. Hallyn" <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: cgroup tasks file error
Date: Mon, 13 Dec 2010 17:27:44 -0800 (PST)	[thread overview]
Message-ID: <478892.90636.qm@web34204.mail.mud.yahoo.com> (raw)

Hi Serge,

Now I cannot move the pid out of the assigned group !

[host:/dev/cgroup]$ cat cpuset.cpus
0
[host:/dev/cgroup]$ cat cpuset.mems
0
[host:/dev/cgroup]$ cat hello/tasks
580

[host:/dev/cgroup]$ echo 580 > tasks
-bash: echo: write error: Operation not permitted

[host:/dev/cgroup]$
[host:/dev/cgroup]$ cd hello
[host:/dev/cgroup/hello]$ cat cpuset.cpus
0
[host:/dev/cgroup/hello]$ cat cpuset.mems
0
[host:/dev/cgroup/hello]



--- On Mon, 12/13/10, ccmail111 <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:

> From: ccmail111 <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> Subject: Re: cgroup tasks file error
> To: "Serge E. Hallyn" <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
> Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Date: Monday, December 13, 2010, 8:23 PM
> Hi Serge,
> 
> Thanks for quick response.
> 
> I had mounted as:
> 
>  mount -t cgroup cpuset /dev/cgroup
> 
> After setting below, it works.
> Thank you for helpful tip !
> 
> 
> --- On Mon, 12/13/10, Serge E. Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
> wrote:
> 
> > From: Serge E. Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
> > Subject: Re: cgroup tasks file error
> > To: "ccmail111" <ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> > Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> > Date: Monday, December 13, 2010, 6:16 PM
> > Quoting ccmail111 (ccmail111-/E1597aS9LQAvxtiuMwx3w@public.gmane.org):
> > > 
> > > I see error:[host:/dev/cgroup]$ echo 693 >
> > hello-test/tasks
> > > -bash: echo: write error: No space left on
> device
> > > [host:/dev/cgroup]$ pwd/dev/cgroup
> > > 
> > > But the user process is up and running..
> > > 
> > > [host:/dev/cgroup]$ ps aux | grep procroot    
>   
> > > 
> > > 693  0.0  0.4  34720  1112 ttyS0    Sl  
> 19:11
> >   0:00 /opt/bin/myproc -ext
> > > 
> > > Also the cgroup exists and valid..
> > > 
> > > [host:/dev/cgroup]$ ls | grep hello-test
> > > hello-test
> > > 
> > > What above error mean and any suggestions ?
> > > Please email.
> > 
> > Which cgroups do you have composed on that mount? 
> I'm
> > guess you
> > have cpuset, and you need to set the cpuset.mems and
> > cpuset.cpus.
> > Until you do that, no tasks can be assigned to it.
> > 
> > -serge
> > 
> 
> 
> 
> 


      

             reply	other threads:[~2010-12-14  1:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14  1:27 ccmail111 [this message]
     [not found] ` <478892.90636.qm-m6GApcO8MwWvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2010-12-14  1:34   ` cgroup tasks file error 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
  -- strict thread matches above, loose matches on Subject: below --
2010-12-13 22:25 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
2010-12-14  1:23       ` 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=478892.90636.qm@web34204.mail.mud.yahoo.com \
    --to=ccmail111-/e1597as9lqavxtiumwx3w@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@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.