diff options
author | Nicolai Hähnle <[email protected]> | 2016-09-07 11:01:17 +0200 |
---|---|---|
committer | Nicolai Hähnle <[email protected]> | 2016-09-27 16:45:11 +0200 |
commit | 5af9eef719cda5e45b69a0cd1fde135df5dd3fbc (patch) | |
tree | 0c55df13f4118cb640557ecdc3c7740268122f57 /src/gallium/winsys/vc4 | |
parent | 6d89a4067627fdf568c6c4e3d9a201fd45d5352b (diff) |
winsys/amdgpu: do not synchronize unsynchronized buffers
When a buffer is added to a CS without the SYNCHRONIZED usage flag, we now
no longer add a dependency on the buffer's fence(s).
However, we still need to add a fence to the buffer during flush, so that
cache reclaim works correctly (and in the hypothetical case that the buffer
is later added to a CS _with_ the SYNCHRONIZED flag).
It is now possible that the submissions refererring to a buffer are no longer
linearly ordered, and so we may have to keep multiple fences around. We keep
the fences in a FIFO. It should usually stay quite short (# of contexts * 2,
for gfx + dma rings).
While we're at it, extract amdgpu_add_fence_dependency for a single buffer,
which will make adding the distinction between real buffer and slab cases
easier.
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/gallium/winsys/vc4')
0 files changed, 0 insertions, 0 deletions