[PATCH] drm/i915/gvt: remove scheduler_mutex in per-engine workload_thread

[Zhenyu Wang]

On 2017.06.19 08:49:17 +0800, Weinan Li wrote:
> For the vGPU workloads, now GVT-g use per vGPU scheduler, the per-ring
> work_thread only pick workload belongs to the current vGPU. And with time
> slice based scheduler, it waits all the engines become idle before do vGPU
> switch. So we can run free dispatch in per-ring work_thread, different ring
> running in different 'vGPU' won't happen.
> 
> For the workloads between vGPU and Host, this scheduler_mutex can't block
> host to dispatch workload into other ring engines.
> 
> Here remove this mutex since it impacts the performance when applications
> use more than 1 ring engines in 1 vgpu.
> 
> ring0 running in vGPU1, ring1 running in Host. Will happen.
> ring0 running in vGPU1, ring1 running in vGPU2. Won't happen.
> 
> Signed-off-by: Weinan Li <weinan.z.li at intel.com>
> Signed-off-by: Ping Gao <ping.a.gao at intel.com>

Pushed, thanks!

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/intel-gvt-dev/attachments/20170620/25c3184a/attachment.sig>