From: "Daniel Hokka Zakrisson" <daniel@hozac.com>
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>
Subject: Re: [RFC][PATCH] introduce task cgroup (#task restrictioon for prevent fork bomb by cgroup)
Date: Thu, 5 Jun 2008 23:52:36 +0200 (CEST) [thread overview]
Message-ID: <41480.192.168.101.12.1212702756.squirrel@intranet> (raw)
In-Reply-To: <20080605132512.9C31.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> Hi
>
> I create new cgroup of number task restriction.
> Please any comments!
Would it make more sense to implement this as part of an rlimit subsystem,
which also supports limiting e.g. address space, CPU time, number of open
files, etc.? If we create one subsystem per resource, I'm afraid we're
going to see quite some time spent in all those loops, and the options for
cgroupfs is going to become pretty long if you want to exclude just one or
two of the subsystems for one particular mount point.
--
Daniel Hokka Zakrisson
next prev parent reply other threads:[~2008-06-05 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 4:43 KOSAKI Motohiro
2008-06-05 5:13 ` KAMEZAWA Hiroyuki
2008-06-05 5:23 ` Daisuke Nishimura
2008-06-05 10:56 ` KOSAKI Motohiro
2008-06-05 5:47 ` Li Zefan
2008-06-05 10:53 ` KOSAKI Motohiro
2008-06-05 9:27 ` Dhaval Giani
2008-06-05 10:51 ` KOSAKI Motohiro
2008-06-05 21:52 ` Daniel Hokka Zakrisson [this message]
2008-06-07 7:41 ` KOSAKI Motohiro
2008-06-07 9:12 ` Paul Menage
2008-06-05 22:04 ` Paul Menage
2008-06-07 6:46 ` 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=41480.192.168.101.12.1212702756.squirrel@intranet \
--to=daniel@hozac.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®