gallium/radeon: remove buffer_unmap calls that can potentially decrease perf
authorMarek Olšák <marek.olsak@amd.com>
Thu, 16 Jul 2015 12:54:50 +0000 (14:54 +0200)
committerMarek Olšák <marek.olsak@amd.com>
Wed, 22 Jul 2015 22:59:24 +0000 (00:59 +0200)
commit5e3974338ed7ea49a41405f8c2e4bcd5fd1f5c80
treeb194a1203454ac94ee7d43c5368e819e4506c416
parent0aa2446e2c18e4a54ccf8555a8ff3426e4eb3ded
gallium/radeon: remove buffer_unmap calls that can potentially decrease perf

buffer_unmap is currently a no-op on radeon and done correctly on amdgpu.
I plan to fix it for radeon, but before that, all occurences of buffer_unmap
that can negatively affect performance in the future must be removed.

There are 2 reasons for removing buffer_unmap calls:
- There is a likelihood that buffer_map will be called again, so we don't
  want to unmap yet.
- The buffer is being released, which automatically unmaps it.

Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
src/gallium/drivers/r300/r300_query.c
src/gallium/drivers/r300/r300_transfer.c
src/gallium/drivers/r600/r600_state_common.c
src/gallium/drivers/radeon/r600_pipe_common.c
src/gallium/drivers/radeon/r600_query.c
src/gallium/drivers/radeon/r600_texture.c
src/gallium/drivers/radeonsi/si_compute.c