From: Greg Stark <gsstark@mit.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrea Arcangeli <andrea@suse.de>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Mike Fedyk <mfedyk@matchmail.com>,
Antonio Vargas <wind@cocodriloo.com>,
lkml <linux-kernel@vger.kernel.org>,
Marc-Christian Petersen <m.c.p@wolk-project.de>
Subject: Re: Andrea VM changes
Date: 15 Sep 2003 01:16:03 -0400 [thread overview]
Message-ID: <87y8wq638s.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <1062339003.10208.1.camel@dhcp23.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sul, 2003-08-31 at 00:19, Andrea Arcangeli wrote:
> > I've an algorithm that will work, and that will provide very good
> > guarantees to kill the "best" task to make the machine usable again,
> > with the needed protection against the security DoSes, but it's in
> > no-way similar to the current oom killer.
>
> And -ac has trivial code so you can avoid OOM killing every happening,
> which is pretty much essential for big servers. Perhaps merging that
> as well would be a good idea.
Indeed there has been an enormous amount of discussion on the postgres mailing
list about how to deal with the OOM killer. The wide consensus there is that
the only sane setting for a production database would be one that guarantees
never to kill overcommit at all.
Frankly, they're a bit in shock that this wasn't an option a long time ago.
Consider e.g.:
http://groups.google.com/groups?threadm=3F510688.1050709%40colorfullife.com
--
greg
next prev parent reply other threads:[~2003-09-15 5:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 15:50 Marcelo Tosatti
2003-08-30 19:11 ` Marcelo Tosatti
2003-08-30 19:21 ` Marcelo Tosatti
2003-08-30 23:19 ` Andrea Arcangeli
2003-08-30 23:30 ` Marcelo Tosatti
2003-08-30 23:57 ` Andrea Arcangeli
2003-08-31 14:10 ` Alan Cox
2003-08-31 14:59 ` Andrea Arcangeli
2003-08-31 15:29 ` Alan Cox
2003-08-31 15:59 ` Andrea Arcangeli
2003-09-15 5:16 ` Greg Stark [this message]
2003-09-15 10:47 ` Andrea Arcangeli
2003-08-31 11:50 ` Matthias Andree
2003-09-01 19:52 ` Mike Fedyk
2003-09-01 17:59 ` Andrea Arcangeli
[not found] <Pine.LNX.4.44.0308311353170.15412-100000@logos.cnet>
2003-09-01 17:27 ` Marcelo Tosatti
2003-09-01 17:50 ` Andrea Arcangeli
[not found] <qL3q.1Pm.3@gated-at.bofh.it>
[not found] ` <qQ37.2q0.9@gated-at.bofh.it>
2003-09-01 9:15 ` Ihar 'Philips' Filipau
-- strict thread matches above, loose matches on Subject: below --
2003-09-01 1:02 Dan Kegel
2003-09-01 6:03 ` Rik van Riel
2003-08-31 17:34 Marcelo Tosatti
2003-08-31 17:34 Marcelo Tosatti
2003-08-31 22:46 ` Andrea Arcangeli
2003-09-01 6:01 ` Rik van Riel
2003-09-01 15:54 ` Andrea Arcangeli
2003-08-31 15:51 Dan Kegel
2003-08-31 15:48 ` Jörn Engel
2003-08-31 16:19 ` Dan Kegel
2003-08-31 19:08 ` Jonathan Lundell
2003-08-31 19:22 ` Chris Frey
2003-08-31 23:42 ` Jamie Lokier
2003-09-01 11:47 ` Alan Cox
2003-08-30 15:13 Marcelo Tosatti
2003-08-30 15:41 ` Andrea Arcangeli
2003-09-01 18:26 ` Marcelo Tosatti
2003-09-01 18:36 ` Andrea Arcangeli
2003-09-01 19:00 ` Marcelo Tosatti
2003-09-01 19:05 ` Andrea Arcangeli
2003-09-02 20:51 ` Marcelo Tosatti
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=87y8wq638s.fsf@stark.dyndns.tv \
--to=gsstark@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=marcelo@conectiva.com.br \
--cc=mfedyk@matchmail.com \
--cc=wind@cocodriloo.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
all inboxes | Powered by JetHome®