Re: [Intel-gfx] [PATCH 37/40] drm/i915: Allow a context to define its set of engines

2018-10-01 Thread Tvrtko Ursulin
On 28/09/2018 21:22, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-09-27 12:28:47) On 19/09/2018 20:55, Chris Wilson wrote: Over the last few years, we have debated how to extend the user API to support an increase in the number of engines, that may be sparse and even be heterogeneous

Re: [Intel-gfx] [PATCH 37/40] drm/i915: Allow a context to define its set of engines

2018-09-28 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-09-27 12:28:47) > > On 19/09/2018 20:55, Chris Wilson wrote: > > Over the last few years, we have debated how to extend the user API to > > support an increase in the number of engines, that may be sparse and > > even be heterogeneous within a class (not all video

Re: [Intel-gfx] [PATCH 37/40] drm/i915: Allow a context to define its set of engines

2018-09-27 Thread Tvrtko Ursulin
On 19/09/2018 20:55, Chris Wilson wrote: Over the last few years, we have debated how to extend the user API to support an increase in the number of engines, that may be sparse and even be heterogeneous within a class (not all video decoders created equal). We settled on using (class, instance)

[Intel-gfx] [PATCH 37/40] drm/i915: Allow a context to define its set of engines

2018-09-19 Thread Chris Wilson
Over the last few years, we have debated how to extend the user API to support an increase in the number of engines, that may be sparse and even be heterogeneous within a class (not all video decoders created equal). We settled on using (class, instance) tuples to identify a specific engine, with