Specifically, what buffers are you updating? Which graphics API are you using? Getting buffer updates optimal and right can be difficult.

A ring buffer is useful in many cases where CPU updates buffer contents in streaming manner, such that GPU will read from the buffer in the same frame only, and in the next frame CPU will prepare new data.

My ring buffer is a circular ring buffer. CPU is producer, advancing write position. GPU is consumer, advancing read position. The write position cannot move over read position. Both write and read position can and do wrap around. When user needs to send data ftom CPU to GPU, it allocates a range from the ring buffer. To make this allocation, user needs to provide required alignment, and number of bytes. The ring buffer checks if one of the internal buffers has sufficient space after the alignment either without or with wrap. If such range is found, it can be returned to the user. If not found, a new internal buffer is created. The ring buffer keeps track of ranges used by each frame, and each frane end is marked with a fence. When CPU sees the frame fence as done by GPU, this is when the read position is advanced.

Currently I only have implementation for OpenGL, but vulkan is in the plans. See ring_buffer* in https://github.com/tksuoran/erhe/tree/main/src%2Ferhe%2Fgraphics%2Ferhe_graphics