On Mon, Oct 6, 2014 at 11:37 AM, Mel Gorman <mgorman@xxxxxxx> 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@xxxxxxxxxxxxxxxxxx>
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@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>