All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrea <andrea256it@yahoo.it>,
	linux-kernel@vger.kernel.org
Subject: Re: super root shell/mode/api
Date: Wed, 20 May 2009 06:36:04 +0200	[thread overview]
Message-ID: <20090520043603.GA9725@1wt.eu> (raw)
In-Reply-To: <20090518161231.GC20244@khazad-dum.debian.net>

On Mon, May 18, 2009 at 01:12:31PM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 18 May 2009, Alan Cox wrote:
> > Your distribution failed to configure your system sensibly in that case.
> > Linux has supported a strict overcommit mode for some years, and in that
> > mode a process isn't permitted to drive the system so far out of memory
> > it locks up or hangs.
> 
> Err... strict overcommit is vm.overcommit_memory=2, right?  That means no
> overcommit at all (as far as the documentation goes, anyway).

exactly

> Which distros enable that by default?

I don't know if mainline distros do this, but some distros dedicated to
embedded systems have been using that for ages, almost since Alan published
his first overcommit patch a long time ago. It's the only way to reach
very long uptimes on servers, as it also protects you against your own
mistakes (eg: stupid actions such as "vi access.log" when the file is
larger than memory).

Willy


  reply	other threads:[~2009-05-20  4:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17 13:06 super root shell/mode/api Andrea
2009-05-17 15:02 ` Andi Kleen
2009-05-18  9:35 ` Alan Cox
2009-05-18 16:12   ` Henrique de Moraes Holschuh
2009-05-20  4:36     ` Willy Tarreau [this message]
2009-05-20  6:03       ` Sitsofe Wheeler
  -- strict thread matches above, loose matches on Subject: below --
2009-05-17 17:13 Andrea
     [not found] <cCSbU-L3-17@gated-at.bofh.it>
2009-05-18 22:56 ` Bodo Eggert
2009-05-19 14:36 Andrea
2009-05-19 14:54 ` Alan Cox
2009-05-23 13:23 ` Bodo Eggert
2009-05-23 13:50 ` Joao Correia

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=20090520043603.GA9725@1wt.eu \
    --to=w@1wt.eu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea256it@yahoo.it \
    --cc=hmh@hmh.eng.br \
    --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 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.