Early on, CPU accessible VRAM memory types were only available on systems with a unified memory architecture

Aperta
#44 0 commenti 2 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
cpp

Direzione di ricerca

Review the Vulkan article section containing “Early on, CPU accessible VRAM” and the note about staging buffers. Start by checking the cited Radeon R300 and Voodoo 1 examples, then assess whether the explanation needs deletion or a specific counterexample and clearer context about VMA, vkAllocateMemory, and vkMapMemory. Done when the misleading or insufficiently nuanced explanation is corrected and the conditions for using a host staging buffer are clear.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

How "early" is this, exactly?

Graphics units as early as Radeon R300 (2002) or Voodoo 1 (1995) support CPU memory-mapped access to on-board video RAM.

I speculate all PCI graphics units have such a feature, including graphics units that predate the Voodoo 1 that don't include "3D" features. Maybe there are some ancient 1980s ISA bus units that only support video RAM accesses via special x86 IO ports. Is such trivia relevant to an article about Vulkan? 🙂

Suggestion: do one of these things:

  • Delete the text starting from "Early on, CPU accessible VRAM" and ending at "make it accessible via the CPU." (the information is misleading and/or not relevant to Vulkan)
  • Give a specific example of the graphics unit you're referring to that does not support CPU memory-mapped video RAM, with additional clarification on how this is relevant for VMA/vkAllocateMemory/vkMapMemory

I do see the note about "so-called "staging" buffer on the host". Perhaps this could be a few sentences longer to explain more precisely when this is necessary? I suspect the current "dedicated GPUs can now map most of their VRAM into host address space" may be an incorrect or insufficiently nuanced explanation.

Lingua principale
C++
Stelle
681
Fork
63
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SaschaWillems/HowToVulkan

Tutte le issue di SaschaWillems/HowToVulkan

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.