From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: Marcelo Tosatti <marcelo@parcelfarce.linux.theplanet.co.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Andrea VM changes
Date: Mon, 1 Sep 2003 17:54:03 +0200 [thread overview]
Message-ID: <20030901155403.GF11503@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0309010200470.25149-100000@chimarrao.boston.redhat.com>
On Mon, Sep 01, 2003 at 02:01:35AM -0400, Rik van Riel wrote:
> On Sun, 31 Aug 2003, Marcelo Tosatti wrote:
>
> > 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?
>
> Usually syslogd, which receives an error message from the
> network driver the moment memory fills up.
>
> The near-certain death of syslogd in OOM situations is why
> I wrote the OOM killer in the first place.
that was used to happen with the old vm, now the fariness in the
allocator is better and normally the first task that runs in the oom
condition is the one that's killed, plus after one task-killing no other
tasks are normally killed (in the past the vm wasn't capable of using
the freed ram promptly and it was killing 3/4 tasks in a row, so syslogd
was killed despite the hog already exited). still you're right syslogd
may be very well still killed in theory but that's ok with me.
Andrea
next prev parent reply other threads:[~2003-09-01 15:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 17:34 Andrea VM changes Marcelo Tosatti
2003-08-31 22:46 ` Andrea Arcangeli
2003-09-01 6:01 ` Rik van Riel
2003-09-01 15:54 ` Andrea Arcangeli [this message]
[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=20030901155403.GF11503@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@parcelfarce.linux.theplanet.co.uk \
--cc=riel@redhat.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