From: Neil Horman <nhorman@tuxdriver.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] vm: enhance __alloc_pages to prioritize pagecache eviction when pressed for memory
Date: Mon, 12 Dec 2005 16:40:43 -0500 [thread overview]
Message-ID: <20051212214043.GC828@hmsreliant.homelinux.net> (raw)
In-Reply-To: <20051212121639.2e5bb1e4.akpm@osdl.org>
On Mon, Dec 12, 2005 at 12:16:39PM -0800, Andrew Morton wrote:
> Neil Horman <nhorman@tuxdriver.com> wrote:
> >
> > On Fri, Dec 09, 2005 at 04:29:01PM -0800, Andrew Morton wrote:
> > > Neil Horman <nhorman@tuxdriver.com> wrote:
> > > >
> > > > Hey all-
> > > > I was recently shown this issue, wherein, if the kernel was kept full of
> > > > pagecache via applications that were constantly writing large amounts of data to
> > > > disk, the box could find itself in a position where the vm, in __alloc_pages
> > > > would invoke the oom killer repetatively within try_to_free_pages, until such
> > > > time as the box had no candidate processes left to kill, at which point it would
> > > > panic.
> > >
> > > That's pretty bad. Are you able to provide a description which would permit
> > > others to reproduce this?
> >
> > As promised, heres the reproducer that was given to me, and used to reproduce
> > this problem:
> >
> > 1) setup an nfs serve with a thread count of 2. Of course, 1 thread might make
> > the problem more easy to reproduce. I haven't tried it yet.
> >
> > 2) Setup 4 nodes to hammer the nfs mounted directory. The 4 nodes should hammer
> > out 4 gigs. 2 gigs didn't seem to be enough.
> >
> > I used a locally developed tool called ior to reproduce this problem. The tool
> > can be found here:
> >
> > http://www.llnl.gov/asci/platforms/purple/rfp/benchmarks/limited/ior/
> >
> > I suppose anything that can write to NFS fast should be fine. But that's what I
> > did.
> >
> >
> > If you do this, any node writing to the server that has more than 4GB of RAM
> > should start oom killing to the point where it runs out of candidate processes
> > and panics
>
> We merged an NFS fix last week which will help throttling under heavy
> writeout conditions..
This one?
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=bb713d6d38f7be4f4e7d790cddb1b076e7da6699
I guess I must have just missed it during my testing. I'll give it a spin and
let you know if it fixes my test case.
Thanks & Regards
Neil
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
/***************************************************
*Neil Horman
*Software Engineer
*gpg keyid: 1024D / 0x92A74FA1 - http://pgp.mit.edu
***************************************************/
next prev parent reply other threads:[~2005-12-12 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 22:04 Neil Horman
2005-12-10 0:29 ` Andrew Morton
2005-12-10 18:25 ` Neil Horman
2005-12-12 18:22 ` Neil Horman
2005-12-12 20:16 ` Andrew Morton
2005-12-12 21:40 ` Neil Horman [this message]
2005-12-14 19:43 ` Neil Horman
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=20051212214043.GC828@hmsreliant.homelinux.net \
--to=nhorman@tuxdriver.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®