From: Peter Zijlstra <peterz@infradead.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: containers@lists.osdl.org, LKML <linux-kernel@vger.kernel.org>,
Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] introduce task cgroup v2
Date: Mon, 16 Jun 2008 09:04:42 +0200 [thread overview]
Message-ID: <1213599882.16944.90.camel@twins> (raw)
In-Reply-To: <20080616155630.78A9.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Mon, 2008-06-16 at 15:59 +0900, KOSAKI Motohiro wrote:
> Hi Peter,
>
> > > # mount -t cgroup -o task none /dev/cgroup
> > > # mkdir /dev/cgroup/foo
> > > # cd /dev/cgroup/foo
> > > # ls
> > > notify_on_release task.max_tasks task.nr_tasks tasks
> > > # echo 100 > task.max_tasks
> > > # echo $$ > tasks
> > > # fork_bomb 1000 & <- try create 1000 process
> > > # pgrep fork_bomb | wc -l
> > > 98
> >
> > fwiw I think the name sucks!
> > cgroups are about grouping tasks, so what's a task cgroup?
>
> Sorry, my english skill is very low.
> I hope restrict number of tasks.
>
> Do you have any name idea?
Sadly I suck at naming too ;-(
perhaps task_limit controller, or nr_tasks controller.
We should preferably pick one that transfers to most other rlimit like
controls.
next prev parent reply other threads:[~2008-06-16 7:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 11:00 [PATCH] introduce task cgroup v2 KOSAKI Motohiro
2008-06-10 5:22 ` Li Zefan
2008-06-16 2:16 ` KOSAKI Motohiro
2008-06-16 7:01 ` Li Zefan
2008-06-16 7:06 ` KOSAKI Motohiro
2008-06-11 7:45 ` Paul Menage
[not found] ` <6599ad830806110045n6aec52ddkfb4be91b685357fe-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-16 1:32 ` KOSAKI Motohiro
2008-06-16 1:32 ` KOSAKI Motohiro
2008-06-21 7:56 ` Paul Menage
2008-06-21 8:56 ` Balbir Singh
[not found] ` <485CC255.9010504-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-06-21 9:10 ` KOSAKI Motohiro
2008-06-21 9:10 ` KOSAKI Motohiro
2008-06-21 15:48 ` Paul Menage
2008-06-21 17:01 ` KOSAKI Motohiro
2008-06-21 17:04 ` Balbir Singh
2008-06-21 17:22 ` KOSAKI Motohiro
2008-06-14 4:46 ` Randy Dunlap
2008-06-16 2:07 ` KOSAKI Motohiro
2008-06-16 6:39 ` Peter Zijlstra
2008-06-16 6:59 ` KOSAKI Motohiro
2008-06-16 7:04 ` Peter Zijlstra [this message]
2008-06-16 7:07 ` Li Zefan
2008-06-16 7:09 ` KOSAKI Motohiro
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=1213599882.16944.90.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
/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.