From: Andrea Arcangeli <andrea@suse.de>
To: Marcelo Tosatti <marcelo@parcelfarce.linux.theplanet.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Andrea VM changes
Date: Mon, 1 Sep 2003 00:46:10 +0200 [thread overview]
Message-ID: <20030831224610.GB24409@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0308311433410.16240-100000@logos.cnet>
On Sun, Aug 31, 2003 at 02:34:01PM -0300, Marcelo Tosatti wrote:
>
>
> ---------- Forwarded message ----------
> Date: Sun, 31 Aug 2003 12:43:27 -0300 (BRT)
> From: Marcelo Tosatti <marcelo@parcelfarce.linux.theplanet.co.uk>
> To: Andrea Arcangeli <andrea@suse.de>
> Cc: 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
>
>
>
> On Sun, 31 Aug 2003, Andrea Arcangeli wrote:
>
> > This oom killer on desktops may do a worse selections of the task to
> > kill (the usual ssh now has a chance to be killed), but it fixes the oom
> > deadlocks and it won't do stupid things on servers shall a netscape or
> > whatever else app hit an userspace bug. So I've to prefer it, until I
> > will write a reliable algorithm for the oom killing that won't fall into
> > dosable corner cases so easily (mlock/nfs/database as the three most
> > common examples of where current mainline can fail, btw the lowmem
> > shortage is another very common DoS that the oom killer will never
> > notice, my tree doesn't deadlock [or at least not technically, in
> > practice it may look like a kernel deadlock despite syscalls returns
> > -ENOMEM ;) ] during lowmem shortage on the 64G boxes).
>
> Suppose you have a big fat hog leaking (lets say, netscape) allocating
> pages at a slow pace. Now you have a decent well behaved app who is
> allocating at a fast pace, and gets killed.
>
> The chance the well behaved app gets killed is big, right?
correct. But it's not a bad thing. How can you know it's better to kill
the hog instead of the well behaved app? if the the hog is allocating at
slow pace, the admin will simply have to kill it if it grown too big. In
terms of omm-killing an hog allocating at slow peace, is no different
from a malloc(1G);bzero(1G);pause(); that leaves 1k free only.
eventually the hog will be killed too if needed.
Andrea
next prev parent reply other threads:[~2003-08-31 22:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 17:34 Marcelo Tosatti
2003-08-31 22:46 ` Andrea Arcangeli [this message]
2003-09-01 6:01 ` Rik van Riel
2003-09-01 15:54 ` 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 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: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
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
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=20030831224610.GB24409@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@parcelfarce.linux.theplanet.co.uk \
/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®