Re: [Intel-gfx] [RFC 0/4] Eliminating the execlist retired request queue

2016-04-11 Thread Chris Wilson
On Mon, Apr 11, 2016 at 10:19:29AM +0100, Tvrtko Ursulin wrote: > > On 09/04/16 09:03, Chris Wilson wrote: > >On Fri, Apr 08, 2016 at 02:54:54PM +0100, Tvrtko Ursulin wrote: > >>From: Tvrtko Ursulin > >> > >>Retired request queue coupled with retired work handler is a

Re: [Intel-gfx] [RFC 0/4] Eliminating the execlist retired request queue

2016-04-11 Thread Tvrtko Ursulin
On 09/04/16 09:03, Chris Wilson wrote: On Fri, Apr 08, 2016 at 02:54:54PM +0100, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Retired request queue coupled with retired work handler is a scalability concern on some workloads of which one dramatic example is

Re: [Intel-gfx] [RFC 0/4] Eliminating the execlist retired request queue

2016-04-09 Thread Chris Wilson
On Fri, Apr 08, 2016 at 02:54:54PM +0100, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Retired request queue coupled with retired work handler is a scalability > concern on some workloads of which one dramatic example is gem_close_race. > > This series depend on

[Intel-gfx] [RFC 0/4] Eliminating the execlist retired request queue

2016-04-08 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Retired request queue coupled with retired work handler is a scalability concern on some workloads of which one dramatic example is gem_close_race. This series depend on i915_gem_object_pin_map series by Chris Wilson. Brief outline of patches: