Re: [Bug #14141] order 2 page allocation failures (generic)

Mel Gorman
2009-10-19T14:06:19Z

On Mon, Oct 19, 2009 at 04:01:45PM +0200, Karol Lewandowski wrote:
> On Mon, Oct 19, 2009 at 12:54:11PM +0300, Pekka Enberg wrote:
> > On Mon, 2009-10-19 at 11:49 +0200, Tobi Oetiker wrote:
> > > I have updated a fileserver to 2.6.31 today and I see page
> > > allocation failures from several parts of the system ... mostly nfs though ... (it is a nfs server).
> > > So I guess the problem must be quite generic:
> >
> > Yup, it almost certainly is. Does this patch help?
> >
> > http://lkml.org/lkml/2009/10/16/89
>
> This patch seems to help in some cases. Before applying this patch I
> was able to trigger alloc failures on different machine by booting
> kernel with "mem=256MB" and doing:
>
> $ gitk on-full-tree &
> # rmmod e100
> ... wait for few MBs in swap
> # modprobe e100; ifup --force ethX
>
> So here this patch helped -- with it, I was unable to trigger page
> allocation failures (testing was short, tough). However, as I said
> here[1], I applied both of Mel's patches (including this one) and that
> didn't help my orginal issue (failures after suspend).
>
> [1] http://lkml.org/lkml/2009/10/17/109
>

Can you test with my kswapd patch applied and commits 373c0a7e,8aa7e847
reverted please?

--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab