From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: davej@redhat.com, AChittenden@bluearc.com,
linux-kernel@vger.kernel.org, lwoodman@redhat.com
Subject: Re: Out of Memory: Killed process 16498 (java).
Date: Fri, 20 Jan 2006 00:23:07 -0800 [thread overview]
Message-ID: <20060120002307.76bcbc27.akpm@osdl.org> (raw)
In-Reply-To: <20060120081231.GE4213@suse.de>
Jens Axboe <axboe@suse.de> wrote:
>
> On Thu, Jan 19 2006, Andrew Morton wrote:
> > Dave Jones <davej@redhat.com> wrote:
> > >
> > > On Thu, Jan 19, 2006 at 03:11:45PM -0000, Andy Chittenden wrote:
> > > > DMA free:20kB min:24kB low:28kB high:36kB active:0kB inactive:0kB
> > > > present:12740kB pages_scanned:4 all_unreclaimable? yes
> > >
> > > Note we only scanned 4 pages before we gave up.
> > > Larry Woodman came up with this patch below that clears all_unreclaimable
> > > when in two places where we've made progress at freeing up some pages
> > > which has helped oom situations for some of our users.
> >
> > That won't help - there are exactly zero pages on ZONE_DMA's LRU.
> >
> > The problem appears to be that all of the DMA zone has been gobbled up by
> > the BIO layer. It seems quite inappropriate that a modern 64-bit machine
> > is allocating tons of disk I/O pages from the teeny ZONE_DMA. I'm
> > suspecting that someone has gone and set a queue's ->bounce_gfp to the wrong
> > thing.
> >
> > Jens, would you have time to investigate please?
>
> Certainly, I'll get this tested and fixed this afternoon.
Wow ;)
You may find it's an x86_64 glitch - setting max_[low_]pfn wrong down in
the bowels of the arch mm init code, something like that.
I thought it might have been a regression which came in when we added
ZONE_DMA32 but the RH reporter is based on 2.6.14-<redhat stuff>, and he
didn't have ZONE_DMA32.
next prev parent reply other threads:[~2006-01-20 8:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 15:11 Out of Memory: Killed process 16498 (java) Andy Chittenden
2006-01-19 19:48 ` Dave Jones
2006-01-19 22:15 ` Andrew Morton
2006-01-20 8:12 ` Jens Axboe
2006-01-20 8:23 ` Andrew Morton [this message]
2006-01-20 12:08 ` Jens Axboe
2006-01-20 12:17 ` Andrew Morton
2006-01-20 12:28 ` Jens Axboe
2006-01-20 12:51 ` Andrew Morton
2006-01-20 1:03 ` Andrew Morton
2006-01-20 1:28 ` Dave Jones
2006-01-20 1:49 ` Andrew Morton
2006-01-21 20:00 ` Dan Aloni
-- strict thread matches above, loose matches on Subject: below --
2006-01-27 11:53 Andy Chittenden
2006-01-27 14:21 ` Jens Axboe
2006-01-27 14:39 ` Anton Altaparmakov
2006-01-23 10:03 Andy Chittenden
2006-01-23 10:11 ` Jens Axboe
2006-01-21 21:47 Andy Chittenden
2006-01-23 9:27 ` Jens Axboe
[not found] <89E85E0168AD994693B574C80EDB9C27035561DE@uk-email.terastack.bluearc.com>
2006-01-20 17:39 ` Jens Axboe
[not found] <89E85E0168AD994693B574C80EDB9C27035560E4@uk-email.terastack.bluearc.com>
2006-01-20 12:37 ` Larry Woodman
[not found] <89E85E0168AD994693B574C80EDB9C2703555F8E@uk-email.terastack.bluearc.com>
2006-01-19 9:44 ` Andrew Morton
2006-01-19 9:40 Andy Chittenden
2006-01-19 9:41 ` Con Kolivas
2006-01-19 8:43 Andy Chittenden
2006-01-19 8:56 ` Andrew Morton
2006-01-19 9:36 ` Con Kolivas
2006-01-19 20:54 ` Martin Bligh
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=20060120002307.76bcbc27.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=AChittenden@bluearc.com \
--cc=axboe@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
/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.