Fixed comment on multiple BLAS generation
This commit is contained in:
parent
7b96b9582c
commit
389f8e58ed
1 changed files with 3 additions and 4 deletions
|
|
@ -599,10 +599,9 @@ vkCmdBuildAccelerationStructuresKHR(cmdBuf, 1, &buildAs[idx].buildInfo, &buildAs
|
||||||
~~~~
|
~~~~
|
||||||
|
|
||||||
|
|
||||||
Note the barrier after each call to the build: this is necessary because we are reusing scratch space across builds,
|
Note the barrier after each call to the build: For the sake of simplicity we are reusing scratch space across builds,
|
||||||
so we need to make sure the previous build is finished before starting the next one. We could have used multiple
|
so we need to make sure the previous build is finished before starting the next one.
|
||||||
scratch buffers, but that would have been memory intensive, and the device can only build one BLAS at a time,
|
Ideally, we should have used multiple regions of a scratch buffer so multiple BLAS could be built simultaneously.
|
||||||
so it wouldn't be any faster.
|
|
||||||
|
|
||||||
~~~~ C
|
~~~~ C
|
||||||
// Since the scratch buffer is reused across builds, we need a barrier to ensure one build
|
// Since the scratch buffer is reused across builds, we need a barrier to ensure one build
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue