From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Aucoin@Houston.RR.com
Cc: "'Tim Schmielau'" <tim@physik3.uni-rostock.de>,
"'Andrew Morton'" <akpm@osdl.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
clameter@sgi.com
Subject: Re: la la la la ... swappiness
Date: Tue, 05 Dec 2006 02:04:09 +1100 [thread overview]
Message-ID: <457438E9.1010503@yahoo.com.au> (raw)
In-Reply-To: <200612041445.kB4EjaGi009655@ms-smtp-05.texas.rr.com>
Aucoin wrote:
>>From: Nick Piggin [mailto:nickpiggin@yahoo.com.au]
>>We had customers see similar incorrect OOM problems, so I sent in some
>>patches merged after 2.6.16. Can you upgrade to latest kernel? (otherwise
>>I guess backporting could be an option for you).
>
>
> I will raise the question of moving the kernel forward one more time before
> release. Can you point me to the patches you mentioned?
These two are the main ones:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=408d85441cd5a9bd6bc851d677a10c605ed8db5f
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4ff1ffb4870b007b86f21e5f27eeb11498c4c077
They shouldn't be too hard to backport.
I'd be interested to know how OOM and page reclaim behaves after these patches
(or with a newer kernel).
Thanks,
Nick
--
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-12-04 15:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612030616.kB36GYBs019873@ms-smtp-03.texas.rr.com>
2006-12-03 8:08 ` la la la la ... swappiness Andrew Morton
2006-12-03 15:40 ` Aucoin
2006-12-03 20:46 ` Tim Schmielau
2006-12-03 23:56 ` Aucoin
2006-12-04 0:57 ` Horst H. von Brand
2006-12-04 4:56 ` Andrew Morton
2006-12-04 5:13 ` Linus Torvalds
2006-12-04 17:03 ` Christoph Lameter
2006-12-04 10:43 ` Nick Piggin
2006-12-04 14:45 ` Aucoin
2006-12-04 15:04 ` Nick Piggin [this message]
2006-12-05 4:02 ` Aucoin
2006-12-05 4:46 ` Linus Torvalds
2006-12-05 6:41 ` Aucoin
2006-12-05 7:01 ` Nick Piggin
2006-12-05 7:26 ` Rene Herman
2006-12-05 13:27 ` Aucoin
2006-12-05 13:49 ` Rene Herman
2006-12-05 13:25 ` Aucoin
2006-12-04 19:02 Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2006-12-04 1:54 Aucoin
2006-12-04 4:59 ` Andrew Morton
2006-12-04 7:22 ` Kyle Moffett
2006-12-04 14:39 ` Aucoin
2006-12-04 16:10 ` Chris Friesen
2006-12-04 17:07 ` Horst H. von Brand
2006-12-04 17:49 ` Aucoin
2006-12-04 18:44 ` Tim Schmielau
2006-12-04 21:28 ` Aucoin
2006-12-04 18:46 ` Horst H. von Brand
2006-12-04 21:43 ` Aucoin
2006-12-04 18:06 ` Andrew Morton
2006-12-04 18:15 ` Christoph Lameter
2006-12-04 18:38 ` Jeffrey Hundstad
2006-12-04 21:25 ` Aucoin
2006-12-04 21:43 ` Andrew Morton
2006-12-04 15:55 ` David Lang
2006-12-04 17:42 ` Aucoin
2006-12-03 6:18 Aucoin
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=457438E9.1010503@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Aucoin@Houston.RR.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
--cc=torvalds@osdl.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