summaryrefslogtreecommitdiffstats
path: root/src/mesa/main/bufferobj.c
diff options
context:
space:
mode:
authorChris Forbes <[email protected]>2014-10-01 19:19:47 +1300
committerChris Forbes <[email protected]>2014-10-16 22:31:43 +1300
commit3d989467f1700219b053317e8aafd2965f051273 (patch)
tree5b8b7e38c503b781d91117a04a12f0d5c9a53fb8 /src/mesa/main/bufferobj.c
parent79d09a4b125e745cc89f9bca336619cbd44d9f95 (diff)
mesa: Add usage history bitfield to buffer objects
In the drivers, we occasionally want to reallocate the backing store for a buffer object; often to avoid waiting for the GPU to be finished with the previous contents. At the point that happens, we don't have a good way of determining where else the buffer object may be bound, and so no good way of determining which dirty flags need to be raised -- it's fairly expensive to go looking at all the possible binding points. Until now, we've considered any BO to be possibly bound as a UBO or TexBO, and flagged all that state to be reemitted. Instead, remember what kinds of binding point this buffer has ever been used with, so that the drivers can flag only what they need. I don't expect these bits to ever be reset, but that doesn't matter for reasonable apps. Signed-off-by: Chris Forbes <[email protected]> Reviewed-by: Anuj Phogat <[email protected]>
Diffstat (limited to 'src/mesa/main/bufferobj.c')
0 files changed, 0 insertions, 0 deletions