resolve_back_buffer_read()

MAYAFLUX_API void MayaFlux::Buffers::resolve_back_buffer_read	(	TransferHandle &	handle,
		const VKBufferResources::GenerationSlot &	slot,
		void *	data,
		size_t	size,
		std::shared_ptr< VKBuffer > &	staging,
		size_t	staging_offset = 0
	)

Wait for a recorded download, then copy it out of staging.

Parameters

handle	Handle from download_back_buffer_async. Nulled on return. A null handle means the slot was host-visible; slot is read directly in that case.
slot	Source slot, needed only for the host-visible path.
data	Destination pointer, at least size bytes.
size	Byte count.
staging	The same staging buffer the copy was recorded against.
staging_offset	The same offset it was recorded at.

Issue every download_back_buffer_async in a batch before resolving any of them; resolving as you go reintroduces the serialisation the split exists to avoid.

Definition at line 331 of file StagingUtils.cpp.

{
    if (!data || size == 0)
        return;
 
    if (!handle) {
        if (slot.mapped_ptr) {
            std::memcpy(data, slot.mapped_ptr, size);
        }
        return;
    }
 
    auto buffer_service = Registry::BackendRegistry::instance()
                              .get_service<Registry::Service::BufferService>();
 
    buffer_service->wait_fenced(handle);
 
    auto& resources = staging->get_buffer_resources();
    buffer_service->invalidate_range(resources.memory, staging_offset, size);
 
    const auto* base = static_cast<const uint8_t*>(staging->get_mapped_ptr());
    std::memcpy(data, base + staging_offset, size);
 
    buffer_service->release_fenced(handle);
    handle.reset();
}

References MayaFlux::Registry::BackendRegistry::get_service(), MayaFlux::Registry::BackendRegistry::instance(), MayaFlux::Buffers::VKBufferResources::GenerationSlot::mapped_ptr, size, and MayaFlux::Registry::Service::BufferService::wait_fenced.

Referenced by MayaFlux::Buffers::DataReadProcessor::collect_result(), download_back_buffer(), and MayaFlux::Buffers::VolumeGridBuffer::read_fields().

Here is the call graph for this function:

Here is the caller graph for this function: