From: Andrew Morton <akpm@google.com>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: OOM killer firing on 2.6.18 and later during LTP runs
Date: Sat, 25 Nov 2006 14:08:16 -0800 [thread overview]
Message-ID: <20061125140816.903b7dc7.akpm@google.com> (raw)
In-Reply-To: <4568B72C.1060801@mbligh.org>
On Sat, 25 Nov 2006 13:35:40 -0800
"Martin J. Bligh" <mbligh@mbligh.org> wrote:
> > The traces are a bit confusing, but I don't actually see anything wrong
> > there. The machine has used up all swap, has used up all memory and has
> > correctly gone and killed things. After that, there's free memory again.
>
> Yeah, it's just a bit odd that it's always in the IO path.
It's not. It's in the main pagecache allocation path for reads.
> Makes me
> suspect there's actually a bunch of pagecache in the box as well,
show_free_areas() doesn't appear to dump the information which is needed to
work out how much of that memory is pagecache and how much is swapcache. I
assume it's basically all swapcache.
> but
> maybe it's just coincidence, and the rest of the box really is full
> of anon mem. I thought we dumped the alt-sysrq-m type stuff on an OOM
> kill, but it seems not. maybe that's just not in mainline.
We do. It's sitting there in your logs.
next prev parent reply other threads:[~2006-11-25 22:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 21:03 OOM killer firing on 2.6.18 and later during LTP runs Martin J. Bligh
2006-11-25 21:28 ` Andrew Morton
2006-11-25 21:35 ` Martin J. Bligh
2006-11-25 22:08 ` Andrew Morton [this message]
2006-11-26 3:00 ` Dave Jones
2006-11-26 7:11 ` Andrew Morton
2006-11-26 7:25 ` Dave Jones
2006-11-26 7:30 ` Andrew Morton
2006-11-26 11:38 ` Andy Whitcroft
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=20061125140816.903b7dc7.akpm@google.com \
--to=akpm@google.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.