From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Mel Gorman <mgorman@suse.de>
Cc: Sarah A Sharp <sarah@thesharps.us>, Linux MM <linux-mm@kvack.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Kswapd 100% CPU since 3.8 on Sandybridge
Date: Mon, 6 Oct 2014 15:32:08 +0200 [thread overview]
Message-ID: <CAKMK7uG8r06rKL=YU4XZhMuUxw_4qOv2vg2+04y1QBGSayPLCA@mail.gmail.com> (raw)
In-Reply-To: <20141006093740.GA19574@suse.de>
On Mon, Oct 6, 2014 at 11:37 AM, Mel Gorman <mgorman@suse.de> wrote:
> Minimally I wanted you to sample the stack traces for kswapd, narrow down
> to the time of its failure and see if it was stuck in a shrinker loop. What
> I suspected at the time was that it was hammering on the i915 shrinker and
> possibly doing repeated shrinks of the GPU objects in there. At one point
> at least, that was an extremely heavy operation if the objections were
> not freeable and I wanted to see if that was still the case. I confess I
> haven't looked at the code to see what has changed recently.
We've stopped doing that with
commit 2cfcd32a929b21c3cf77256dd8b858c076803ccc
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Tue May 20 08:28:43 2014 +0100
drm/i915: Implement an oom-notifier for last resort shrinking
so now we do the handbreak last ditch shrinking really only when the
mm decided that it's time to oom. Until that point we should just do
the proportional shrinking the vm asked us to, but not more.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-10-06 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABe+QzA=0YVpQ8rN+3X-cbH6JP1nWTvp2spb93P9PqJhmjBROA@mail.gmail.com>
[not found] ` <CABe+QzA-E40bFFXYJBc663Kx0KrE3xy2uZq5xOH2XL6mFPA6+w@mail.gmail.com>
2014-10-04 17:05 ` Sarah A Sharp
2014-10-06 7:25 ` Daniel Vetter
2014-10-06 9:37 ` Mel Gorman
2014-10-06 13:32 ` Daniel Vetter [this message]
2014-10-26 16:05 ` sarah
2014-10-26 18:20 ` Johannes Weiner
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='CAKMK7uG8r06rKL=YU4XZhMuUxw_4qOv2vg2+04y1QBGSayPLCA@mail.gmail.com' \
--to=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=sarah@thesharps.us \
/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