mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-02-25 07:10:31 +01:00
0ce346368f
Until know when we consumed a barrier we would implement it by setting the serialize flag on a job, which would cause it to be serialized across all hardware queues (CL, CSD, TFU). However, now that we track the source(s) of the barrier, we can restrict this to only the relevant queue(s) instead (multisync path only). It should be noted that we can implement transfers via TFU or CL jobs, so if the source of a barrier is a transfer, we currently synchronize against both the TFU and the CL queues, however, we may be able to more effectively track this in the future to restrict this to just one of the queues. Also, for secondary command buffers we are taking the easy way out and always synchronize against all queues, but we should be able to do the same for secondaries without too much effort. Reviewed-by: Alejandro Piñeiro <apinheiro@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16743> |
||
|---|---|---|
| .. | ||
| ci | ||
| cle | ||
| clif | ||
| common | ||
| compiler | ||
| drm-shim | ||
| qpu | ||
| simulator | ||
| vulkan | ||
| .editorconfig | ||
| meson.build | ||