If we are waiting for the currently executing request, we have a good
idea that it will be completed in the very near future and so want to
cap the CPU_DMA_LATENCY to ensure that we wake up the client quickly.
v2: Not allowed to block in kmalloc after setting TASK_INTERRUPTIBLE.
v3: Avoid the bloc
If we are waiting for the currently executing request, we have a good
idea that it will be completed in the very near future and so want to
cap the CPU_DMA_LATENCY to ensure that we wake up the client quickly.
Testcase: igt/gem_sync/store-default
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc
If we are waiting for the currently executing request, we have a good
idea that it will be completed in the very near future and so want to
cap the CPU_DMA_LATENCY to ensure that we wake up the client quickly.
Testcase: igt/gem_sync/store-default
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc