From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-mm@kvack.org
Subject: Re: [patch 0/9] oom: various fixes and improvements for 2.6.18-rc2
Date: Fri, 28 Jul 2006 00:44:10 -0700 [thread overview]
Message-ID: <20060728004410.63bba676.akpm@osdl.org> (raw)
In-Reply-To: <20060515210529.30275.74992.sendpatchset@linux.site>
On Fri, 28 Jul 2006 09:20:44 +0200 (CEST)
Nick Piggin <npiggin@suse.de> wrote:
> These are some various OOM killer fixes that I have accumulated. Some of
> the more important ones are in SLES10, and were developed in response to
> issues coming up in stress testing.
>
> The other small fixes haven't been widely tested, but they're issues I
> spotted when working in this area.
>
> Comments?
They all look good to me (although I haven't grappled with the cpuset ones
yet).
The "oom: reclaim_mapped on oom" one is kinda funny. Back in 2.5.early I
decided that we were probably donig too much scanning before declaring oom
so I randomly reduced it by a factor of, iirc, four. Under the assumption
that someone would start hitting early ooms and would get in there and tune
it for real. It took five years ;)
Which of these patches have been well-tested and which are the more
speculative ones?
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-07-28 7:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 7:20 Nick Piggin
2006-07-28 7:20 ` [patch 1/9] oom: use unreclaimable info Nick Piggin
2006-07-28 7:21 ` [patch 2/9] oom: reclaim_mapped on oom Nick Piggin
2006-07-28 7:21 ` [patch 3/9] cpuset: oom panic fix Nick Piggin
2006-07-28 7:29 ` Nick Piggin
2006-07-28 9:06 ` Paul Jackson
2006-07-28 7:21 ` [patch 4/9] oom: cpuset hint Nick Piggin
2006-07-28 9:07 ` Paul Jackson
2006-07-28 7:21 ` [patch 5/9] oom: handle current exiting Nick Piggin
2006-07-28 7:21 ` [patch 6/9] oom: handle oom_disable exiting Nick Piggin
2006-07-28 7:21 ` [patch 7/9] oom: swapoff tasks tweak Nick Piggin
2006-07-28 7:21 ` [patch 8/9] oom: kthread infinite loop fix Nick Piggin
2006-07-28 7:22 ` [patch 9/9] oom: more printk Nick Piggin
2006-07-28 7:44 ` Andrew Morton [this message]
2006-07-28 9:28 ` [patch 0/9] oom: various fixes and improvements for 2.6.18-rc2 Nick Piggin
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=20060728004410.63bba676.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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