From 513a7ca417a3d26d995b68fc065db85088cf7d6c Mon Sep 17 00:00:00 2001 From: Karol Herbst Date: Sat, 21 Jun 2025 22:26:11 +0200 Subject: [PATCH] rusticl/queue: do not block when dropping a queue There is no need for a blocking wait anymore now that event processing doesn't depend on the queue anymore. Reviewed-by: Adam Jackson Part-of: --- src/gallium/frontends/rusticl/core/queue.rs | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/gallium/frontends/rusticl/core/queue.rs b/src/gallium/frontends/rusticl/core/queue.rs index d60c8423a8d..8605f909643 100644 --- a/src/gallium/frontends/rusticl/core/queue.rs +++ b/src/gallium/frontends/rusticl/core/queue.rs @@ -466,11 +466,8 @@ impl Queue { impl Drop for Queue { fn drop(&mut self) { - // when deleting the application side object, we have to flush - // From the OpenCL spec: - // clReleaseCommandQueue performs an implicit flush to issue any previously queued OpenCL - // commands in command_queue. - // TODO: maybe we have to do it on every release? - let _ = self.flush(true); + // When reaching this point the queue should have been flushed already, but do it here once + // again just to be sure. + let _ = self.flush(false); } }