public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	containers@lists.osdl.org, LKML <linux-kernel@vger.kernel.org>,
	Paul Menage <menage@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] introduce task cgroup v2
Date: Mon, 16 Jun 2008 15:07:07 +0800	[thread overview]
Message-ID: <4856111B.4000106@cn.fujitsu.com> (raw)
In-Reply-To: <1213599882.16944.90.camel@twins>

Peter Zijlstra wrote:
> 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.
> 

We have memrlimit in -mm currently, which controls address space.

  reply	other threads:[~2008-06-16  7:08 UTC|newest]

Thread overview: 21+ 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
2008-06-16  1:32   ` KOSAKI Motohiro
2008-06-21  7:56     ` Paul Menage
2008-06-21  8:56       ` Balbir Singh
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
2008-06-16  7:07       ` Li Zefan [this message]
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=4856111B.4000106@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.osdl.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=peterz@infradead.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