From: Szabolcs Szakacsits <szaka@f-secure.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Linus Torvalds <torvalds@transmeta.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Looking for better VM
Date: Wed, 8 Nov 2000 12:34:02 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.4.21.0011081052010.1242-100000@fs129-190.f-secure.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10011061954520.26327-100000@humbolt.nl.linux.org>
On Mon, 6 Nov 2000, Rik van Riel wrote:
> On Mon, 6 Nov 2000, Szabolcs Szakacsits wrote:
> > On Wed, 1 Nov 2000, Rik van Riel wrote:
> > > but simply because
> > > it appears there has been amazingly little research on this
> > > subject and it's completely unknown which approach will work
> > There has been lot of research, this is the reason most Unices support
> > both non-overcommit and overcommit memory handling default to
> > non-overcommit [think of reliability and high availability].
> It's a shame you didn't take the trouble to actually
> go out and see that non-overcommit doesn't solve the
> "out of memory" deadlock problem.
Read my *entire* email again and please try to understand. No deadlock
at all since kernel *falls back* to process killing if memory reserved
for *root* is also out.
You could ask, so what's the point for non-overcommit if we use
process killing in the end? And the answer, in *practise* this almost
never happens, root can always clean up and no processes are lost
[just as when disk is "full" except the reserved area for root]. See?
Human get a chance against hard-wired AI.
I also didn't say non-overcommit should be used as default and a
patch http://www.cs.helsinki.fi/linux/linux-kernel/2000-13/1208.html,
developed for 2.3.99-pre3 by Eduardo Horvath and unfortunately was
ignored completely, implemented it this way.
And with a runtime tunable OOM killer, Linux really would beat the
competitors [where it is quite behind at present] in this area. See?
Human get a chance against hard-wired AI again.
Believe me, there are people [don't read only kernel lists] who wants
a reliable and controllable system and where the kernel doesn't play
Russan rulet.
[who missed my first email: forget about mem quotas and the the
non-scalable "add GB's of swap" in this discussion].
> [if you want an explanation, look in the archives,
> we've explained this a dozen times now]
I've been reading the list much longer than you and really pissed of
that after so many years of discussions, this problem and user
requirements^Wwishes are still not understood. You think black and
white but the world is colorful.
Szaka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next parent reply other threads:[~2000-11-08 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.05.10011061954520.26327-100000@humbolt.nl.linux.org>
2000-11-08 11:34 ` Szabolcs Szakacsits [this message]
2000-11-08 13:53 ` Rik van Riel
2000-11-08 16:36 ` Mikulas Patocka
2000-11-08 17:03 ` Christoph Rohland
2000-11-08 20:52 ` Ingo Oeser
2000-11-09 0:08 ` Rik van Riel
2000-11-09 17:30 ` [PATCH] Reserve VM for root (was: Re: Looking for better VM) Szabolcs Szakacsits
2000-11-10 10:38 ` Andrey Savochkin
2000-11-13 23:44 ` user beancounter (was: Reserve VM for root) Szabolcs Szakacsits
2000-11-08 14:53 Looking for better VM Jesse Pollard
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=Pine.LNX.4.21.0011081052010.1242-100000@fs129-190.f-secure.com \
--to=szaka@f-secure.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
--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