KhronosGroup / KhronosGroup/Vulkan-Tutorial

Make staging optional

Open
#135 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
418
Forks
126
Avg merge
11d 6h
Merged PRs (30d)
31

Description

The content of the staging chapter is pretty much the same as it was in the original tutorial. But that was written at a time where (Re)BAR/SAM where not a thing on desktop.

But with pretty much desktop GPU now offering a device local + host visible memory type just like unified architectures (iGPUs, Mobile), staging is now mostly no longer necessary. At least not for buffers.

We should update the staging chapter accordingly.

That chapter also seems to have outdated information (limit of 4096 memory allocs on nvidia), that needs to be updated too.

Contributor guide

Open the contributing guide

Research direction

Open the staging chapter and review its explanation of when staging is needed for buffers, especially on desktop GPUs with device-local and host-visible memory. Verify the chapter's statement about the NVIDIA memory-allocation limit against current information. Done means the chapter reflects current guidance and removes or updates outdated claims.

Written by the indexing model from the issue text.

Assessment

Domain
computer-graphics, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.