From: Glauber Costa <glommer@parallels.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
<linux-kernel@vger.kernel.org>,
<containers@lists.linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] new cgroup controller "fork"
Date: Thu, 3 Nov 2011 17:25:07 -0200 [thread overview]
Message-ID: <4EB2EA93.2050206@parallels.com> (raw)
In-Reply-To: <20111103192039.GA5300@Debian-60-squeeze-64-minimal>
On 11/03/2011 05:20 PM, Max Kellermann wrote:
> On 2011/11/03 20:03, Alan Cox<alan@lxorguk.ukuu.org.uk> wrote:
>> Sure - I'm just not seeing that a whole separate cgroup for it is
>> appropriate or a good plan. Anyone doing real resource management needs
>> the rest of the stuff anyway.
>
> Right. When I saw Frederic's controller today, my first thought was
> that one could move the fork limit code over into that controller. If
> we reach a consensus that this would be a good idea, and would have
> chances to get merged, I could probably take some time to refactor my
> code.
>
> Max
I'd advise you to take a step back and think if this is really needed.
As Alan pointed out, the really expensive resource here is already being
constrained by Frederic's controller.
But ultimately, you're the only one that knows about your real
requirements.
next prev parent reply other threads:[~2011-11-03 19:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 16:22 [PATCH] new cgroup controller "fork" Max Kellermann
2011-11-03 16:43 ` Frederic Weisbecker
2011-11-03 17:16 ` Max Kellermann
2011-11-03 17:26 ` Glauber Costa
2011-11-03 17:48 ` Max Kellermann
2011-11-03 17:50 ` Glauber Costa
2011-11-03 18:30 ` Max Kellermann
2011-11-03 18:34 ` Glauber Costa
2011-11-03 16:43 ` Glauber Costa
2011-11-03 16:59 ` Max Kellermann
2011-11-03 17:05 ` Frederic Weisbecker
2011-11-03 18:21 ` Alan Cox
2011-11-03 18:51 ` Max Kellermann
2011-11-03 18:56 ` Glauber Costa
2011-11-03 20:08 ` Matt Helsley
2011-11-03 19:03 ` Alan Cox
2011-11-03 19:20 ` Max Kellermann
2011-11-03 19:25 ` Glauber Costa [this message]
2011-11-03 20:13 ` Brian K. White
2011-11-03 21:54 ` Glauber Costa
2011-11-04 3:03 ` Li Zefan
2011-11-04 4:37 ` KAMEZAWA Hiroyuki
2011-11-04 13:11 ` Glauber Costa
2011-11-04 13:38 ` Max Kellermann
2011-11-04 13:59 ` Lennart Poettering
2011-11-03 17:31 ` richard -rw- weinberger
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 13:31 Max Kellermann
2011-02-17 13:50 ` KAMEZAWA Hiroyuki
2011-02-17 14:09 ` Max Kellermann
2011-02-18 0:59 ` Paul Menage
2011-02-18 9:26 ` Max Kellermann
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=4EB2EA93.2050206@parallels.com \
--to=glommer@parallels.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=containers@lists.linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.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