From: Max Kellermann <mk@cm4all.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
Li Zefan <lizf@cn.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Tim Hockin <thockin@hockin.org>
Subject: Re: [PATCH] new cgroup controller "fork"
Date: Thu, 3 Nov 2011 18:16:45 +0100 [thread overview]
Message-ID: <20111103171645.GA27887@rabbit.intern.cm-ag> (raw)
In-Reply-To: <20111103164302.GE8198@somewhere.redhat.com>
On 2011/11/03 17:43, Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Please have a look at the task counter subsystem: https://lwn.net/Articles/461462/
>
> It's in the -mm tree. I'm glad to hear about another user who wants
> this feature in cgroups. We need to hear about you and whether this
> meets your requirements in order to get it merged upstream.
Had a quick look at your patch set. No, it does not seem to meet my
requirements. It limits the number of processes in a cgroup - that is
also very useful, but is different from my controller.
My controller limits the number of fork() calls, not the number of
processes running at a time.
I've been using it for 7 years to put an upper bound on CGI resource
usage in a shared hosting environment at my employer (initially based
on a proprietary cgroup-like subsystem I wrote, when cgroups were not
available yet).
Max
next prev parent reply other threads:[~2011-11-03 17:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 16:22 Max Kellermann
2011-11-03 16:43 ` Frederic Weisbecker
2011-11-03 17:16 ` Max Kellermann [this message]
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
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=20111103171645.GA27887@rabbit.intern.cm-ag \
--to=mk@cm4all.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=thockin@hockin.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
Powered by JetHome