Make staging optional

Open
#135 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

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.

Dominant language
C++
Stars
424
Forks
127
Avg merge
2d 22h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KhronosGroup/Vulkan-Tutorial

All issues in KhronosGroup/Vulkan-Tutorial

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.