All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Barry K. Nathan" <barryn@pobox.com>,
	linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com,
	alan@redhat.com
Subject: Re: [PATCH] strict VM overcommit accounting for 2.4.32/2.4.33-pre1
Date: Fri, 30 Dec 2005 19:33:08 +0100	[thread overview]
Message-ID: <20051230183308.GA2501@w.ods.org> (raw)
In-Reply-To: <1135966666.2941.32.camel@laptopd505.fenrus.org>

On Fri, Dec 30, 2005 at 07:17:46PM +0100, Arjan van de Ven wrote:
> On Fri, 2005-12-30 at 18:48 +0100, Willy Tarreau wrote:
> > On Thu, Dec 29, 2005 at 11:44:01PM -0800, Barry K. Nathan wrote:
> > > This patch adds strict VM overcommit accounting to the mainline 2.4
> > > kernel, thus allowing overcommit to be truly disabled. This feature
> > > has been in 2.4-ac, Red Hat Enterprise Linux 3 (RHEL 3) vendor kernels,
> > > and 2.6 for a long while.
> > 
> > Many thanks, I'm impatient to try it ! I tried to backport it in the
> > past but miserably failed as I don't understand those areas well. I'm
> > interested in checking that a buggy service cannot eat all the RAM an
> > bring the machine to death.
> 
> that's what rlimit is for though... overcommit acounting doesn't help
> you a lot there.

Not always. When you have buggy apache modules eating lots of memory and
you have tons of processes, rlimit will be of limited help.

> Also I think, to be honest, that this is a feature that is getting
> unsuitable for the "bugfixes only" 2.4 kernel series....

Agreed, it really is too late IMHO, because there's a non-null risk of
introducing new bugs with it. It would have been cool a few months
earlier. That won't stop me from trying it in my own tree however ;-)

Willy


  reply	other threads:[~2005-12-30 18:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30  7:44 [PATCH] strict VM overcommit accounting for 2.4.32/2.4.33-pre1 Barry K. Nathan
2005-12-30 17:48 ` Willy Tarreau
2005-12-30 18:17   ` Arjan van de Ven
2005-12-30 18:33     ` Willy Tarreau [this message]
2005-12-30 19:37       ` Barry K. Nathan
2005-12-30 20:45         ` Willy Tarreau
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30 20:06 Al Boldi
2005-12-30 20:18 ` Barry K. Nathan
2005-12-30 20:51   ` Al Boldi
2005-12-30 21:44     ` Willy TARREAU
2005-12-31  0:55 ` Alan Cox
2005-12-31  4:59   ` Al Boldi
2005-12-31  7:38     ` Willy Tarreau
2005-12-31 14:02       ` Al Boldi
2005-12-31 14:18         ` Willy Tarreau
2005-12-31 14:26         ` Arjan van de Ven
2005-12-31 14:58           ` Willy Tarreau
2005-12-31 15:17             ` Arjan van de Ven
2005-12-31 17:36           ` Al Boldi
2006-01-01  9:12             ` Arjan van de Ven

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=20051230183308.GA2501@w.ods.org \
    --to=willy@w.ods.org \
    --cc=alan@redhat.com \
    --cc=arjan@infradead.org \
    --cc=barryn@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.