tu: Move vsc_data and vsc_data2 allocation into the device
authorConnor Abbott <cwabbott0@gmail.com>
Tue, 28 Jan 2020 16:30:44 +0000 (17:30 +0100)
committerConnor Abbott <cwabbott0@gmail.com>
Wed, 5 Feb 2020 14:27:28 +0000 (15:27 +0100)
commit8455648ccae92692e4a522d23b1491d5825b030c
tree2c6afa1c86f900fa5b448b163d931416e8d7b7eb
parent84bd4da468cd21dad5d41110b495b08623e82a0e
tu: Move vsc_data and vsc_data2 allocation into the device

In addition to preparing us for dynamically resizing them, which has to
be controlled by the device, this greatly reduces the memory usage when
allocating large numbers of command buffers, making
dEQP-VK.api.object_management.max_concurrent.command_buffer_primary go
from crash -> pass.

Reviewed-by: Kristian H. Kristensen <hoegsberg@gmail.com>
Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3621>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3621>
src/freedreno/vulkan/tu_cmd_buffer.c
src/freedreno/vulkan/tu_device.c
src/freedreno/vulkan/tu_private.h