diff options
| author | Nicolai Hähnle <[email protected]> | 2017-11-10 11:15:44 +0100 |
|---|---|---|
| committer | Nicolai Hähnle <[email protected]> | 2017-11-20 18:16:15 +0100 |
| commit | 3f17d3c01753020ff01e8d30a25edff6ca453971 (patch) | |
| tree | b8c3611bc8b1e1807ca9e74530a444df8beebdad /src/gallium/drivers/radeonsi/si_fence.c | |
| parent | bc65dcab3bc48673ff6180afb036561a4b8b1119 (diff) | |
gallium/u_threaded: avoid syncing in threaded_context_flush
We could always do the flush asynchronously, but if we're going to wait
for a fence anyway and the driver thread is currently idle, the additional
communication overhead isn't worth it.
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/gallium/drivers/radeonsi/si_fence.c')
| -rw-r--r-- | src/gallium/drivers/radeonsi/si_fence.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/gallium/drivers/radeonsi/si_fence.c b/src/gallium/drivers/radeonsi/si_fence.c index 5163d652c83..9d6bcfe1027 100644 --- a/src/gallium/drivers/radeonsi/si_fence.c +++ b/src/gallium/drivers/radeonsi/si_fence.c @@ -203,7 +203,8 @@ static boolean si_fence_finish(struct pipe_screen *screen, * be in flight in the driver thread, so the fence * may not be ready yet when this call returns. */ - threaded_context_flush(ctx, rfence->tc_token); + threaded_context_flush(ctx, rfence->tc_token, + timeout == 0); } if (timeout == PIPE_TIMEOUT_INFINITE) { |