From: Jonathan Miles <jon@cybus.co.uk>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, David John <davidjon@xenontk.org>,
penberg@cs.helsinki.fi
Subject: Re: OOM kernel behaviour - 2.6.32
Date: Fri, 04 Dec 2009 20:36:06 +0000 [thread overview]
Message-ID: <4B1972B6.1060408@cybus.co.uk> (raw)
In-Reply-To: <4B155B4A.9050405@cybus.co.uk>
On 01/12/09 18:07 Jonathan Miles said the following:
> It's Ubuntu's (Karmic) 2.6.31 .deb and I don't know exactly what they've
> done to it, but AFAIK, no containers or policies. I'll compile 2.6.31.6
> and test with that. Won't be able to do this until Friday, so will check
> back in then.
Everything is fine having compiled straight 2.6.32. I watched the cache
being reclaimed with top as I used more and more RAM and didn't see the
OOM killer being invoked. So it was either a problem with 2.6.31 or with
whatever Ubuntu did to make the .deb.
Thanks,
--
Jonathan Miles <jon@cybus.co.uk>
http://www.linkedin.com/in/jonmiles
next prev parent reply other threads:[~2009-12-04 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 17:38 OOM kernel behaviour Jonathan Miles
2009-11-30 18:57 ` Christoph Lameter
2009-12-01 9:57 ` Jonathan Miles
2009-12-01 13:21 ` Jonathan Miles
2009-12-01 16:08 ` Christoph Lameter
2009-12-01 18:07 ` Jonathan Miles
2009-12-01 18:42 ` Christoph Lameter
2009-12-04 20:36 ` Jonathan Miles [this message]
2009-12-09 13:52 ` OOM kernel behaviour - 2.6.32 Jonathan Miles
2009-12-01 15:35 ` OOM kernel behaviour David John
2009-12-01 16:07 ` Christoph Lameter
2009-12-01 17:10 ` David John
2009-12-01 17:26 ` Christoph Lameter
2009-12-02 15:55 ` Mel Gorman
2009-12-07 5:34 ` David John
2009-12-07 14:59 ` Mel Gorman
2009-12-08 3:41 ` David John
2009-12-01 17:32 ` Christoph Lameter
2009-12-02 3:17 ` David John
2009-12-02 4:29 ` KOSAKI Motohiro
2009-12-02 5:24 ` David John
2009-12-02 5:31 ` KOSAKI Motohiro
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=4B1972B6.1060408@cybus.co.uk \
--to=jon@cybus.co.uk \
--cc=cl@linux-foundation.org \
--cc=davidjon@xenontk.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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