[Vulkan] New docs for buffer cache

This commit is contained in:
DrChat 2018-02-09 20:57:26 -06:00
parent a1677d34e1
commit 3ad45f4186
1 changed files with 7 additions and 8 deletions

View File

@ -860,14 +860,13 @@ bool VulkanCommandProcessor::PopulateVertexBuffers(
// TODO: Make the buffer cache ... actually cache buffers. We can have // TODO: Make the buffer cache ... actually cache buffers. We can have
// a list of buffers that were cached, and store those in chunks in a // a list of buffers that were cached, and store those in chunks in a
// multiple of the host's page size. // multiple of the host's page size.
// WRITE WATCHES: We need to invalidate vertex buffers if they're written // So, we need to track all vertex buffers in a sorted map, and track all
// to. Since most vertex buffers aren't aligned to a page boundary, this // write watches in a sorted map. When a vertex buffer is uploaded, track
// means a watch may cover more than one vertex buffer. // all untracked pages with 1-page write watches. In the callback,
// We need to maintain a list of write watches, and what memory ranges // invalidate any overlapping vertex buffers.
// they cover. If a vertex buffer lies within a write watch's range, assign //
// it to the watch. If there's partial alignment where a buffer lies within // We would keep the old transient buffer as a staging buffer, and upload
// one watch and outside of it, should we create a new watch or extend the // to a GPU-only buffer that tracks all cached vertex buffers.
// existing watch?
auto buffer_ref = buffer_cache_->UploadVertexBuffer( auto buffer_ref = buffer_cache_->UploadVertexBuffer(
current_setup_buffer_, physical_address, source_length, current_setup_buffer_, physical_address, source_length,
static_cast<Endian>(fetch->endian), current_batch_fence_); static_cast<Endian>(fetch->endian), current_batch_fence_);