linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Andrew Lutomirski <luto@mit.edu>,
	Minchan Kim <minchan.kim@gmail.com>,
	linux-mm <linux-mm@kvack.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Root-causing kswapd spinning on Sandy Bridge laptops?
Date: Mon, 27 Jun 2011 12:03:02 +0100	[thread overview]
Message-ID: <20110627110302.GT9396@suse.de> (raw)
In-Reply-To: <1308941289-sup-5157@shiny>

On Fri, Jun 24, 2011 at 02:54:11PM -0400, Chris Mason wrote:
> Excerpts from Andi Kleen's message of 2011-06-24 14:44:12 -0400:
> > Andrew Lutomirski <luto@mit.edu> writes:
> > 
> > [Putting the Intel graphics driver developers in cc.]
> > 
> > > I'm back :-/
> > >
> > > I just triggered the kswapd bug on 2.6.39.1, which has the
> > > cond_resched in shrink_slab.  This time my system's still usable (I'm
> > > tying this email on it), but kswapd0 is taking 100% cpu.  It *does*
> > > schedule (tested by setting its affinity the same as another CPU hog
> > > and confirming that each one gets 50%).
> > >
> > > It appears to be calling i915_gem_inactive_shrink in a loop.  I have
> > > probes on entry and return of i915_gem_inactive_shrink and on return
> > > of shrink_slab.  I see:
> > >
> > >          kswapd0    47 [000] 59599.956573: mm_vmscan_kswapd_wake: nid=0 order=0
> > >          kswapd0    47 [000] 59599.956575: shrink_zone:
> > > (ffffffff810c848c) priority=12 zone=ffff8801005fe000
> > >          kswapd0    47 [000] 59599.956576: shrink_zone_return:
> > > (ffffffff810c848c <- ffffffff810c96c6) arg1=0
> > >          kswapd0    47 [000] 59599.956578: i915_gem_inactive_shrink:
> 
> A similar trace came up a bunch of times in Jejb's NMI softlockup/kswapd
> consumes the machine thread.  That one was tracked down to slub high
> order allocations.
> 
> I'm sure that one is burned in on Mel's memory, but after a while the
> individual traces fell out of the thread, and I'm not sure the i915 part
> stuck out.
> 

I expect that Jejb's lockup is also fixed by "Stop kswapd consuming
100% CPU when highest zone is small". i915 didn't help but at the end
of the day, kswapd shouldn't have been shrinking slab so aggressively.

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-06-27 11:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  6:22 Root-causing kswapd spinning on Sandy Bridge laptops? Andrew Lutomirski
2011-06-24  9:27 ` Minchan Kim
2011-06-24  9:38   ` Minchan Kim
2011-06-24 10:24   ` Pádraig Brady
2011-06-24 12:15     ` Pádraig Brady
2011-06-24 12:51     ` Mel Gorman
2011-06-24 13:32       ` Andrew Lutomirski
2011-06-24 18:44 ` Andi Kleen
2011-06-24 18:48   ` Andrew Lutomirski
2011-06-24 19:13     ` Andi Kleen
2011-06-24 19:17       ` Christoph Hellwig
2011-06-24 18:54   ` Chris Mason
2011-06-27 11:03     ` Mel Gorman [this message]
2011-06-27 20:18       ` James Bottomley

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=20110627110302.GT9396@suse.de \
    --to=mgorman@suse.de \
    --cc=andi@firstfloor.org \
    --cc=chris.mason@oracle.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@mit.edu \
    --cc=minchan.kim@gmail.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;
as well as URLs for NNTP newsgroup(s).