[Bug 111090] 3% perf drop in GfxBench Manhattan 3.0, 3.1 and CarChase test-cases

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Aug 2 23:15:26 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=111090

--- Comment #13 from Chris Wilson <chris at chris-wilson.co.uk> ---
Wrt the jump in shrinker activity, I hope 

commit 1aff1903d0ff53f055088a77948ac8d8224d42db
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Fri Aug 2 22:21:36 2019 +0100

    drm/i915: Hide unshrinkable context objects from the shrinker

    The shrinker cannot touch objects used by the contexts (logical state
    and ring). Currently we mark those as "pin_global" to let the shrinker
    skip over them, however, if we remove them from the shrinker lists
    entirely, we don't event have to include them in our shrink accounting.

    By keeping the unshrinkable objects in our shrinker tracking, we report
    a large number of objects available to be shrunk, and leave the shrinker
    deeply unsatisfied when we fail to reclaim those. The shrinker will
    persist in trying to reclaim the unavailable objects, forcing the system
    into a livelock (not even hitting the dread oomkiller).

    v2: Extend unshrinkable protection for perma-pinned scratch and guc
    allocations (Tvrtko)
    v3: Notice that we should be pinned when marking unshrinkable and so the
    link cannot be empty; merge duplicate paths.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Reviewed-by: Matthew Auld <matthew.auld at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20190802212137.22207-1-chris@chris-wilson.co.uk

helps (by making the shrinker less aggressive towards us)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190802/5db42b45/attachment.html>


More information about the intel-gfx-bugs mailing list