From: Willy Tarreau <willy@w.ods.org>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: 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 18:48:17 +0100 [thread overview]
Message-ID: <20051230174817.GW15993@alpha.home.local> (raw)
In-Reply-To: <20051230074401.GA7501@ip68-225-251-162.oc.oc.cox.net>
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.
Cheers,
Willy
next prev parent reply other threads:[~2005-12-30 17:51 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 [this message]
2005-12-30 18:17 ` Arjan van de Ven
2005-12-30 18:33 ` Willy Tarreau
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=20051230174817.GW15993@alpha.home.local \
--to=willy@w.ods.org \
--cc=alan@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox