From: Daniel Phillips <phillips@arcor.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marc-Christian Petersen <m.c.p@gmx.net>
Cc: 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 04:07:43 +0200 [thread overview]
Message-ID: <E17iQL2-0001VV-00@starship> (raw)
In-Reply-To: <1030037573.3090.3.camel@irongate.swansea.linux.org.uk>
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?
--
Daniel
next prev parent reply other threads:[~2002-08-24 2:02 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 [this message]
2002-08-24 3:46 ` Rik van Riel
2002-08-24 13:42 ` Daniel Phillips
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=E17iQL2-0001VV-00@starship \
--to=phillips@arcor.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@gmx.net \
/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®