On Tue, 30 Jul 2019 at 14:31, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > > 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@xxxxxxxxxxxxxxxxxx> > Cc: Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxx> Reviewed-by: Matthew Auld <matthew.auld@xxxxxxxxx> _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
