From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Al Boldi <a1426z@gawab.com>
Cc: barryn@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] strict VM overcommit accounting for 2.4.32/2.4.33-pre1
Date: Sat, 31 Dec 2005 00:55:02 +0000 [thread overview]
Message-ID: <1135990502.28365.43.camel@localhost.localdomain> (raw)
In-Reply-To: <200512302306.28667.a1426z@gawab.com>
On Gwe, 2005-12-30 at 23:06 +0300, Al Boldi wrote:
> > +3 - (NEW) paranoid overcommit The total address space commit
> > + for the system is not permitted to exceed swap. The machine
> > + will never kill a process accessing pages it has mapped
> > + except due to a bug (ie report it!)
>
> This one isn't in 2.6, which is critical for a stable system.
Actually it is
In the 2.4 case we took "50% RAM + swap" as the safe sane world 'never
OOM kill' and to all intents and purposes it works. We also had a 100%
paranoia mode.
When it was ported to 2.6 (not by me) whoever did it very sensibly made
the percentage tunable and removed "mode 3" since its mode 2 0% ram and
can be set that way.
Alan
next prev parent reply other threads:[~2005-12-31 0:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 20:06 [PATCH] strict VM overcommit accounting for 2.4.32/2.4.33-pre1 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-12-30 7:44 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
2005-12-30 19:37 ` Barry K. Nathan
2005-12-30 20:45 ` Willy Tarreau
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=1135990502.28365.43.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=a1426z@gawab.com \
--cc=barryn@pobox.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