On 28/07/2018 17:46, Chris Wilson wrote:
Here we bump the busyspin for the current request to avoid sleeping and
the cost of both idling and downclocking the CPU.

Signed-off-by: Chris Wilson <ch...@chris-wilson.co.uk>
Cc: Sagar Kamble <sagar.a.kam...@intel.com>
Cc: Eero Tamminen <eero.t.tammi...@intel.com>
Cc: Francisco Jerez <curroje...@riseup.net>
Cc: Tvrtko Ursulin <tvrtko.ursu...@intel.com>
Cc: Ben Widawsky <b...@bwidawsk.net>
Cc: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
Cc: Michał Winiarski <michal.winiar...@intel.com>
---
  drivers/gpu/drm/i915/Kconfig.profile | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/Kconfig.profile 
b/drivers/gpu/drm/i915/Kconfig.profile
index de394dea4a14..54e0ba4051e7 100644
--- a/drivers/gpu/drm/i915/Kconfig.profile
+++ b/drivers/gpu/drm/i915/Kconfig.profile
@@ -1,6 +1,6 @@
  config DRM_I915_SPIN_REQUEST_IRQ
        int
-       default 5 # microseconds
+       default 250 # microseconds
        help
          Before sleeping waiting for a request (GPU operation) to complete,
          we may spend some time polling for its completion. As the IRQ may


But the histograms from previous patch do not suggest 250us busy spin gets us into interesting territory. And we have to know the distribution between IRQ and CS spins.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reply via email to