From: Mel Gorman <mel@csn.ul.ie>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
cl@linux-foundation.org
Subject: Re: iwlagn: order 2 page allocation failures
Date: Tue, 8 Sep 2009 11:54:15 +0100 [thread overview]
Message-ID: <20090908105415.GD28127@csn.ul.ie> (raw)
In-Reply-To: <1252226116.11274.10.camel@penberg-laptop>
On Sun, Sep 06, 2009 at 11:35:16AM +0300, Pekka Enberg wrote:
> On Sun, 2009-09-06 at 10:28 +0200, Frans Pop wrote:
> > On Sunday 06 September 2009, Pekka Enberg wrote:
> > > On Sun, Sep 6, 2009 at 10:40 AM, Frans Pop<elendil@planet.nl> wrote:
> > > > Got a couple of page allocation failures today while viewing fairly
> > > > large images. System was struggling for a bit to reorganize memory
> > > > and swap, but nothing really serious. Everything recovered fairly
> > > > quickly.
> > > >
> > > > Anything to look into?
> > > >
> > > > System: HP 2510p; 2.6.31-rc7-56-g7c0a57d; Debian stable, KDE desktop
> > > >
> > > > 10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless
> > > > 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61)
> > >
> > > Can you post your .config, please?
> >
> > Attached. Thanks.
>
> OK, so SLUB_DEBUG_ON is disabled so it's probably not a SLUB problem.
> Mel, there's quite a few page allocation failure reports recently which
> makes me wonder if we broke something with the page allocator
> optimization patches? Do you think the anti-fragmentation fixlet you did
> for nommu would help here?
>
No, because that change only affected the case where the system had very
little memory. The last time that there was a sudden major increase in
allocation failures, it was actually was page reclaim was broken -
specifically kswapd was no longer doing the job that was expected of it.
The symptoms where applications stalling because they were entering
direct reclaim. I haven't looked very closely at this bug report yet
(catching up from being offline the last 5 days).
Have there been any reclaim changes that might account for something like this?
My feeling is also that a number of these page allocation failures have
been related to wireless drivers. Is that accurate? If so, have there
been changes made to the wireless stack in this cycle that would have
increased the order of pages allocated?
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2009-09-08 10:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 7:40 iwlagn: order 2 page allocation failures Frans Pop
2009-09-06 8:14 ` Pekka Enberg
2009-09-06 8:28 ` Frans Pop
2009-09-06 8:35 ` Pekka Enberg
2009-09-08 10:54 ` Mel Gorman [this message]
2009-09-08 11:11 ` Pekka Enberg
2009-09-08 14:17 ` John W. Linville
2009-09-08 14:59 ` Larry Finger
2009-09-09 15:04 ` Mel Gorman
2009-09-09 15:59 ` Frans Pop
2009-09-09 16:55 ` Mel Gorman
2009-09-09 17:19 ` Frans Pop
2009-09-16 14:36 ` Frans Pop
2009-09-16 15:02 ` Mel Gorman
2009-09-16 15:37 ` Frans Pop
2009-09-16 16:26 ` reinette chatre
2009-09-09 20:05 ` reinette chatre
2009-09-10 1:48 ` Frans Pop
2009-09-10 9:02 ` Mel Gorman
2009-09-10 18:15 ` reinette chatre
2009-09-10 18:43 ` Frans Pop
2009-09-10 18:50 ` reinette chatre
2009-09-11 8:45 ` Mel Gorman
2009-09-11 16:14 ` reinette chatre
2009-09-10 21:14 ` reinette chatre
2009-09-11 8:47 ` Mel Gorman
2009-09-14 3:01 ` Zhu Yi
2009-09-14 13:06 ` Mel Gorman
2009-09-15 8:30 ` alloc skb based on a given data buffer Zhu Yi
2009-09-15 8:33 ` David Miller
2009-09-15 8:57 ` Zhu Yi
2009-09-15 9:09 ` David Miller
2009-09-15 9:15 ` Zhu Yi
2009-09-15 15:30 ` Johannes Berg
2009-09-15 21:16 ` David Miller
2009-09-19 5:56 ` Johannes Berg
2009-09-14 15:42 ` iwlagn: order 2 page allocation failures Christoph Lameter
2009-09-14 17:59 ` Mel Gorman
2009-09-14 18:04 ` Christoph Lameter
2009-09-10 8:18 ` Pekka Enberg
2009-09-10 12:34 ` Mel Gorman
2009-09-10 12:39 ` Pekka Enberg
2009-09-10 12:58 ` Mel Gorman
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=20090908105415.GD28127@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).