From: Andrea Arcangeli <andrea@suse.de>
To: Jens Axboe <axboe@suse.de>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: oom killer gone nuts
Date: Fri, 21 Jan 2005 09:05:20 +0100 [thread overview]
Message-ID: <20050121080520.GA7703@dualathlon.random> (raw)
In-Reply-To: <20050121074203.GH2755@suse.de>
On Fri, Jan 21, 2005 at 08:42:08AM +0100, Jens Axboe wrote:
> And especially not with 500MB of zone normal free, thanks :)
;) Are you sure you had 500m free even before the _first_ oom killing?
I assumed what you posted was not the first one of the oom killing
messages. If it was the first then there was a regression. But if OTOH I
didn't misunderstood your message and it wasn't the first, then what
you've seen is just the brokeness of 2.6 w.r.t. oom killing, that's what
made Thomas drive a few hours too, and you've only to apply the 5
patches I just posted, and everything will work perfectly correct then
in terms of _not_ killing right and left anymore, even despite the 500m
free ;). I tested the code before posting and my regression test passed
at least, so it looked like there was no other regression. The several
rejects I've got while porting the code looked all due noop-cleanups. So
I doubt there was a regression and I'm optimistic you've just seen the
old bugs.
next prev parent reply other threads:[~2005-01-21 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 12:34 oom killer gone nuts Jens Axboe
2005-01-20 13:15 ` Andries Brouwer
2005-01-20 14:00 ` Marcelo Tosatti
2005-01-20 18:15 ` Andries Brouwer
2005-01-20 17:15 ` Andrea Arcangeli
2005-01-20 20:52 ` Andries Brouwer
2005-01-20 21:57 ` Chris Friesen
2005-01-20 23:27 ` Andrea Arcangeli
2005-01-21 7:42 ` Jens Axboe
2005-01-21 8:05 ` Andrea Arcangeli [this message]
2005-01-21 8:09 ` Jens Axboe
2005-01-21 8:41 ` Andrea Arcangeli
2005-01-21 8:46 ` Jens Axboe
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=20050121080520.GA7703@dualathlon.random \
--to=andrea@suse.de \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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