mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Paul Menage <paul@paulmenage.org>, Li Zefan <lizf@cn.fujitsu.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Aditya Kali <adityakali@google.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Tim Hockin <thockin@hockin.org>, Tejun Heo <tj@kernel.org>,
	Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH 10/10] cgroups: Add a task counter subsystem
Date: Tue, 11 Oct 2011 15:41:14 +0200	[thread overview]
Message-ID: <20111011134106.GB16777@somewhere.redhat.com> (raw)
In-Reply-To: <20111006092348.GB28820@shutemov.name>

On Thu, Oct 06, 2011 at 12:23:48PM +0300, Kirill A. Shutemov wrote:
> On Mon, Oct 03, 2011 at 09:07:12PM +0200, Frederic Weisbecker wrote:
> > Add a new subsystem to limit the number of running tasks,
> > similar to the NR_PROC rlimit but in the scope of a cgroup.
> > 
> > The user can set an upper bound limit that is checked every
> > time a task forks in a cgroup or is moved into a cgroup
> > with that subsystem binded.
> > 
> > The primary goal is to protect against forkbombs that explode
> > inside a container. The traditional NR_PROC rlimit is not
> > efficient in that case because if we run containers in parallel
> > under the same user, one of these could starve all the others
> > by spawning a high number of tasks close to the user wide limit.
> > 
> > This is a prevention against forkbombs, so it's not deemed to
> > cure the effects of a forkbomb when the system is in a state
> > where it's not responsive. It's aimed at preventing from ever
> > reaching that state and stop the spreading of tasks early.
> > While defining the limit on the allowed number of tasks, it's
> > up to the user to find the right balance between the resource
> > its containers may need and what it can afford to provide.
> > 
> > As it's totally dissociated from the rlimit NR_PROC, both
> > can be complementary: the cgroup task counter can set an upper
> > bound per container and the rlmit can be an upper bound on the
> > overall set of containers.
> > 
> > Also this subsystem can be used to kill all the tasks in a cgroup
> > without races against concurrent forks, by setting the limit of
> > tasks to 0, any further forks can be rejected. This is a good
> > way to kill a forkbomb in a container, or simply kill any container
> > without the need to retry an unbound number of times.
> > 
> > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> 
> Acked-by: Kirill A. Shutemov <kirill@shutemov.name>

Thanks a lot for your acks Kirill!

  reply	other threads:[~2011-10-11 13:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 19:07 [PATCH 00/10] cgroups: Task counter subsystem v6 Frederic Weisbecker
2011-10-03 19:07 ` [PATCH 01/10] cgroups: Add res_counter_write_u64() API Frederic Weisbecker
2011-10-04  0:17   ` Kirill A. Shutemov
2011-10-11 13:44     ` Frederic Weisbecker
2011-10-03 19:07 ` [PATCH 02/10] cgroups: New resource counter inheritance API Frederic Weisbecker
2011-10-04  0:20   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 03/10] cgroups: Add previous cgroup in can_attach_task/attach_task callbacks Frederic Weisbecker
2011-10-04  0:22   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 04/10] cgroups: New cancel_attach_task subsystem callback Frederic Weisbecker
2011-10-04  0:27   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 05/10] cgroups: Ability to stop res charge propagation on bounded ancestor Frederic Weisbecker
2011-10-04  0:41   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 06/10] cgroups: Add res counter common ancestor searching Frederic Weisbecker
2011-10-03 19:07 ` [PATCH 07/10] res_counter: Allow charge failure pointer to be null Frederic Weisbecker
2011-10-04  1:30   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 08/10] cgroups: Pull up res counter charge failure interpretation to caller Frederic Weisbecker
2011-10-04  1:32   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 09/10] cgroups: Allow subsystems to cancel a fork Frederic Weisbecker
2011-10-04  1:38   ` Kirill A. Shutemov
2011-10-03 19:07 ` [PATCH 10/10] cgroups: Add a task counter subsystem Frederic Weisbecker
2011-10-06  9:23   ` Kirill A. Shutemov
2011-10-11 13:41     ` Frederic Weisbecker [this message]
2011-10-04 22:01 ` [PATCH 00/10] cgroups: Task counter subsystem v6 Andrew Morton
2011-10-11 13:40   ` Frederic Weisbecker
2011-10-25 20:06   ` Tim Hockin
2011-10-28 23:30     ` Andrew Morton
2011-10-29  9:38       ` Glauber Costa
2011-11-03 16:49         ` Frederic Weisbecker
2011-11-03 16:58           ` Glauber Costa
2011-11-03 17:02             ` Paul Menage
2011-11-03 17:06               ` Glauber Costa
2011-11-03 17:28                 ` Paul Menage
2011-11-03 17:35                   ` Glauber Costa
2011-11-03 17:56                     ` Paul Menage
2011-11-04 13:17                       ` Glauber Costa
2011-11-03 17:00       ` Frederic Weisbecker
2011-11-04  2:57         ` Li Zefan
2011-11-04 12:37           ` Frederic Weisbecker
2011-10-06  6:51 ` Li Zefan
2011-10-11 13:41   ` Frederic Weisbecker
2011-12-13 15:58 ` Tejun Heo
2011-12-13 19:06   ` Frederic Weisbecker
2011-12-13 20:49     ` Tejun Heo
2011-12-14 15:07       ` Frederic Weisbecker

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=20111011134106.GB16777@somewhere.redhat.com \
    --to=fweisbec@gmail.com \
    --cc=adityakali@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kay.sievers@vrfy.org \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=oleg@redhat.com \
    --cc=paul@paulmenage.org \
    --cc=thockin@hockin.org \
    --cc=tj@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

all inboxes | Powered by JetHome®