From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: the oom killer
Date: Thu, 11 Apr 2002 22:15:33 +0100 [thread overview]
Message-ID: <20020411221533.A20867@infradead.org> (raw)
In-Reply-To: <20020405164348.K32431@dualathlon.random> <Pine.LNX.4.21.0204051844521.11472-100000@freak.distro.conectiva> <20020411151353.K14605@dualathlon.random> <3CB5E6E4.981B8C0D@zip.com.au>
On Thu, Apr 11, 2002 at 12:41:24PM -0700, Andrew Morton wrote:
> It'd be nice if the second and subsequent passes of the oom
> killer were able to note that a kill was already outstanding,
> so they don't just kill the same process all the time.
-rmap uses a simple timeout for that. And I've just send the
rmap oom_killer tweaks to Marcelo so they hopefully will appear
in mainline soon.
prev parent reply other threads:[~2002-04-11 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 9:18 the oom killer Andrew Morton
2002-04-05 14:43 ` Andrea Arcangeli
2002-04-05 21:45 ` Marcelo Tosatti
2002-04-11 13:13 ` Andrea Arcangeli
2002-04-11 19:41 ` Andrew Morton
2002-04-11 21:15 ` Christoph Hellwig [this message]
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=20020411221533.A20867@infradead.org \
--to=hch@infradead.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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