From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Love <rml@tech9.net>,
akpm@zip.com.au, riel@conectiva.com.br,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] 2.5-rmap: VM strict overcommit
Date: Tue, 30 Jul 2002 00:20:52 +0200 [thread overview]
Message-ID: <20020729222052.GA15219@elf.ucw.cz> (raw)
In-Reply-To: <1027694803.13428.43.camel@irongate.swansea.linux.org.uk>
Hi!
> > In what scenario can "strict overcommit" kill?
>
> When the kernel grabs over 50% of RAM. Remember that includes page
> tables. I've seen the kernel taking 35% of RAM.
But it could happen that kernel would attempt to allocate 101% of RAM
for page tables, right? At that even "paranoid overcommit" might be
OOM, right?
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-07-30 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 17:59 [PATCH] 2.5-rmap: VM strict overcommit Robert Love
2002-07-26 10:31 ` Pavel Machek
2002-07-26 14:46 ` Alan Cox
2002-07-29 22:20 ` Pavel Machek [this message]
2002-07-30 17:49 ` Rik van Riel
2002-07-30 17:55 ` William Lee Irwin III
2002-07-30 20:09 ` Alan Cox
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=20020729222052.GA15219@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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