From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: akpm@osdl.org, Nick Piggin <piggin@cyberone.com.au>, andrea@suse.de
Cc: linux-mm@kvack.org
Subject: [barry@disus.com: RE: FW: OOM Killer problem since linux 2.6.8.1]
Date: Mon, 7 Feb 2005 15:53:26 -0200 [thread overview]
Message-ID: <20050207175326.GB5378@logos.cnet> (raw)
FYI.
Success report on Andrea's OOM killer fixes!
----- Forwarded message from barry <barry@disus.com> -----
From: barry <barry@disus.com>
Date: Mon, 7 Feb 2005 14:29:56 -0500
To: 'Marcelo Tosatti' <marcelo.tosatti@cyclades.com>
Cc: andrea@suse.de
Subject: RE: FW: OOM Killer problem since linux 2.6.8.1
Hi Marcelo,
It has been a long time since we last communicated. We worked on my
problem of spurious OOM when there was plenty of swap space available
last September/October.
I am just writing to tell you that the patch set below (in the
2.6.11-rc3 kernel) seems to have fixed the OOM problem that has been
plaguing me since 2.6.8.1..... (IE, I have been manually inserting a fix
for every kernel since then...)
Please thank Andrea for me.....
[PATCH] mm: fix several oom killer bugs
Fix several oom killer bugs, most important avoid spurious oom kills
badness algorithm tweaked by Thomas Gleixner to deal with fork bombs
This is the core of the oom-killer fixes I developed partly taking
the idea from Thomas's patches of getting feedback from the exit
path, plus I moved the oom killer into page_alloc.c as it should to
be able to check the watermarks before killing more stuff. This
also tweaks the badness to take thread bombs more into account (that
change to badness is from Thomas, from my part I'd rather rewrite
badness from scratch instead, but that's an orthgonal issue ;).
With this applied the oom killer is very sane, no more 5 sec waits
and suprious oom kills.
Signed-off-by: Andrea Arcangeli <andrea@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Barry Silverman Phone: 416-368-7677 x234
Disus Inc. Cell: 416-407-8091
110 Spadina #705 Email: barry@disus.com
Toronto, Ontario M5V 2K4
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2005-02-07 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050207175326.GB5378@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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