Linux Container Development
 help / color / mirror / Atom feed
From: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Avinash Chiganmi <avinash.ca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Cgroups: Cannot move certain kernel threads from root cgroup
Date: Mon, 23 Jul 2012 08:11:52 -0500	[thread overview]
Message-ID: <20120723131152.GA4923@sergelap> (raw)
In-Reply-To: <CAGt76inhheRoxVKkDqdE4gxZVemKUmAL2GbUCbBSDJ5hmpHtzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Quoting Avinash Chiganmi (avinash.ca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> Hi,
> 
> I created a "cpu" cgroup:
>      mkdir /dev/cgroup
>      mkdir /dev/cgroup/cpu
>      mount -t cgroup -o cpu cpu /dev/cgroup/cpu
>      cd /dev/cgroup/cpu/
>      mkdir low
> 
> Now, I try to move tasks to the sub-cgroup "low":
>      for task in `cat /dev/cgroup/cpu/tasks`; do   /bin/echo $task >
> /dev/cgroup/cpu/low/tasks || echo "Failed to move PID $task"; done
> 
> /bin/echo: write error: Invalid argument
> Failed to move PID 3
> /bin/echo: write error: Invalid argument
> Failed to move PID 4
> /bin/echo: write error: Invalid argument
> Failed to move PID 5
> /bin/echo: write error: Invalid argument
> Failed to move PID 6
> /bin/echo: write error: Invalid argument
> Failed to move PID 7
> /bin/echo: write error: Invalid argument
> Failed to move PID 8
> /bin/echo: write error: Invalid argument
> .
> .
> .
> /bin/echo: write error: Invalid argument
> Failed to move PID 58
> 
> I was able to move the "init" process itself. However, I failed to move
> specific kernel threads:
> 
> root         3     2  0 18:16 ?        00:00:00 [migration/0]
> root         4     2  0 18:16 ?        00:00:00 [sirq-high/0]
> root         5     2  0 18:16 ?        00:00:04 [sirq-timer/0]
> root         6     2  0 18:16 ?        00:00:00 [sirq-net-tx/0]
> root         7     2  0 18:16 ?        00:00:00 [sirq-net-rx/0]
> root         8     2  0 18:16 ?        00:00:00 [sirq-block/0]
> root         9     2  0 18:16 ?        00:00:00 [sirq-block-iopo]
> root        10     2  0 18:16 ?        00:00:00 [sirq-tasklet/0]
> root        11     2  0 18:16 ?        00:00:00 [sirq-sched/0]
> root        12     2  0 18:16 ?        00:00:00 [sirq-hrtimer/0]
> root        13     2  0 18:16 ?        00:00:04 [sirq-rcu/0]
> root        14     2  0 18:16 ?        00:00:00 [watchdog/0]
> root        15     2  0 18:16 ?        00:00:00 [desched/0]
> root        16     2  0 18:16 ?        00:00:00 [migration/1]
> root        17     2  0 18:16 ?        00:00:00 [sirq-high/1]
> root        18     2  0 18:16 ?        00:00:03 [sirq-timer/1]
> root        19     2  0 18:16 ?        00:00:00 [sirq-net-tx/1]
> root        20     2  0 18:16 ?        00:00:00 [sirq-net-rx/1]
> root        21     2  0 18:16 ?        00:00:00 [sirq-block/1]
> 
> 
> Is there something special about these threads that prevents them from
> being moved to a different cgroup? Is there something I am missing?
> 
> Thanks!
> Avi.

I'm guessing:

kernel/cgroup.c:attach_task_by_pid():

        /*
         * Workqueue threads may acquire PF_THREAD_BOUND and become
         * trapped in a cpuset, or RT worker may be born in a cgroup
         * with no rt_runtime allocated.  Just say no.
         */
        if (tsk == kthreadd_task || (tsk->flags & PF_THREAD_BOUND)) {
                ret = -EINVAL;
                rcu_read_unlock();
                goto out_unlock_cgroup;
        }

      parent reply	other threads:[~2012-07-23 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21 19:23 Cgroups: Cannot move certain kernel threads from root cgroup Avinash Chiganmi
     [not found] ` <CAGt76inhheRoxVKkDqdE4gxZVemKUmAL2GbUCbBSDJ5hmpHtzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-23 13:11   ` Serge Hallyn [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=20120723131152.GA4923@sergelap \
    --to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=avinash.ca-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox