mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2025-12-24 13:10:10 +01:00
ee6e2bc4a3
At image bind time, if an image's addresses can be placed into the aux-map without causing conflicts with a pre-existing mapping, do so. The code aux management code in the binding function operates on a per-plane basis. So, use the per-plane CCS memory range from the image rather than the CCS memory region for the entire BO. Another way to avoid aux-map conflicts is to rely solely on having a dedicated allocation for an image. Unfortunately, not all workloads change their behavior when drivers report a preference for dedicated allocations. In particular, 3DMark Wild Life Extreme does not make more dedicated allocations and such a solution was measured to perform ~16% worse than this solution. With this solution, I did not measure a loss of CCS on that benchmark. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6304 Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> (v1) Reviewed-by: Jianxun Zhang <jianxun.zhang@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25003> |
||
|---|---|---|
| .. | ||
| blorp | ||
| ci | ||
| common | ||
| compiler | ||
| dev | ||
| ds | ||
| genxml | ||
| isl | ||
| nullhw-layer | ||
| perf | ||
| tools | ||
| vulkan | ||
| vulkan_hasvk | ||
| meson.build | ||