mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marc-Christian Petersen <m.c.p@gmx.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: 2.4 kernel series and the oom_killer and /proc/sys/vm/overcommit_memory
Date: Sat, 24 Aug 2002 15:42:18 +0200	[thread overview]
Message-ID: <E17ibBD-0001XZ-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44L.0208240045310.1857-100000@imladris.surriel.com>

On Saturday 24 August 2002 05:46, Rik van Riel wrote:
> On Sat, 24 Aug 2002, Daniel Phillips wrote:
> > On Thursday 22 August 2002 19:32, Alan Cox wrote:
> > > 3 is a totally paranoid [overcommit policy] that will require everything in
> > > ram can be dumped to swap or paged back from backing store
> >
> > How do you handle the situation where you have a lot of shared memory in a
> > half-paged-out state, so that each shared page consumes both ram and swap?
> 
> That will work fine with 'totally paranoid' mode.  There is always
> enough swap space to hold _all_ pages, so everything will just
> continue to work.

Apparently, maximum available memory is limited to

  physical memory + (swap - physical memory) = just swap

in this case, and if swap is smaller than (the potentially swappable portion
of) physical memory you might as well just turn it off.

-- 
Daniel

      reply	other threads:[~2002-08-24 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-22 15:19 Marc-Christian Petersen
2002-08-22 17:22 ` Robert Love
2002-08-22 17:32 ` Alan Cox
2002-08-24  2:07   ` Daniel Phillips
2002-08-24  3:46     ` Rik van Riel
2002-08-24 13:42       ` Daniel Phillips [this message]

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=E17ibBD-0001XZ-00@starship \
    --to=phillips@arcor.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@gmx.net \
    --cc=riel@conectiva.com.br \
    /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®