zink: stop unmapping resources
authorMike Blumenkrantz <michael.blumenkrantz@gmail.com>
Tue, 26 Jan 2021 23:10:13 +0000 (18:10 -0500)
committerMarge Bot <eric+marge@anholt.net>
Thu, 8 Apr 2021 03:34:49 +0000 (03:34 +0000)
commitf19946ca6ecd236592e136a2c45e9bce329f691c
treeac69bb7fd81331c569cf39b63440a862d5337a53
parenteab985d070c94917b743058eedfcc6eedcded418
zink: stop unmapping resources

it turns out there's not actually a requirement that resources be unmapped,
which means that a ton of overhead can be saved both in the unmap codepath
(the cpu overhead here is pretty insane) and then also when mapping cached
resource memory, as the map can now be added to the cache for immediate reuse

as seen in radeonsi

Reviewed-by: Dave Airlie <airlied@redhat.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9980>
src/gallium/drivers/zink/zink_resource.c
src/gallium/drivers/zink/zink_resource.h
src/gallium/drivers/zink/zink_screen.c
src/gallium/drivers/zink/zink_screen.h