From: Chris Forbes Date: Wed, 1 Oct 2014 06:19:47 +0000 (+1300) Subject: mesa: Add usage history bitfield to buffer objects X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=3d989467f1700219b053317e8aafd2965f051273;p=mesa.git 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 Reviewed-by: Anuj Phogat --- diff --git a/src/mesa/main/mtypes.h b/src/mesa/main/mtypes.h index 5e9453b2fd7..881c26ca3bc 100644 --- a/src/mesa/main/mtypes.h +++ b/src/mesa/main/mtypes.h @@ -1464,6 +1464,14 @@ struct gl_buffer_mapping { }; +/** + * Usages we've seen for a buffer object. + */ +typedef enum { + USAGE_UNIFORM_BUFFER = 0x1, +} gl_buffer_usage; + + /** * GL_ARB_vertex/pixel_buffer_object buffer object */ @@ -1481,6 +1489,7 @@ struct gl_buffer_object GLboolean Written; /**< Ever written to? (for debugging) */ GLboolean Purgeable; /**< Is the buffer purgeable under memory pressure? */ GLboolean Immutable; /**< GL_ARB_buffer_storage */ + gl_buffer_usage UsageHistory; /**< How has this buffer been used so far? */ struct gl_buffer_mapping Mappings[MAP_COUNT]; };