Re: [Intel-gfx] [PATCH 03/11] drm/i915: Stop tracking MRU activity on VMA

2018-07-10 Thread Tvrtko Ursulin
On 10/07/2018 13:37, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-07-10 13:19:51) On 09/07/2018 14:02, Chris Wilson wrote: Our goal is to remove struct_mutex and replace it with fine grained locking. One of the thorny issues is our eviction logic for reclaiming space for an execbuffer

Re: [Intel-gfx] [PATCH 03/11] drm/i915: Stop tracking MRU activity on VMA

2018-07-10 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-07-10 13:19:51) > > On 09/07/2018 14:02, Chris Wilson wrote: > > Our goal is to remove struct_mutex and replace it with fine grained > > locking. One of the thorny issues is our eviction logic for reclaiming > > space for an execbuffer (or GTT mmaping, among a few

Re: [Intel-gfx] [PATCH 03/11] drm/i915: Stop tracking MRU activity on VMA

2018-07-10 Thread Tvrtko Ursulin
On 09/07/2018 14:02, Chris Wilson wrote: Our goal is to remove struct_mutex and replace it with fine grained locking. One of the thorny issues is our eviction logic for reclaiming space for an execbuffer (or GTT mmaping, among a few other examples). While eviction itself is easy to move under a

[Intel-gfx] [PATCH 03/11] drm/i915: Stop tracking MRU activity on VMA

2018-07-09 Thread Chris Wilson
Our goal is to remove struct_mutex and replace it with fine grained locking. One of the thorny issues is our eviction logic for reclaiming space for an execbuffer (or GTT mmaping, among a few other examples). While eviction itself is easy to move under a per-VM mutex, performing the activity