Good afternoon,
Working through multi-threading for the first time and following along with HMH up to day 131 where Casey introduces the separate LowPriorityQueue for the FillGroundChunks.
Where I'm a bit lost is how the new low priority threads are getting kicked off? In the previous high priority queue (RenderQueue), PlatformCompleteAllWork() was called at the end to process the queue. For FillGroundChunks, the rendering doesn't process through TiledRenderGroupToOutput and so no complete all work is called.
I believe my understanding gap is around the complete all work. Does the infinite for loop in the threadproc keep the 2 low priority threads always spinning and when Addentry is called they just process? Is the complete all work function only there to ensure all work is completed before the next frame for rendering?
Thanks in advance,
Mebourne
Working through multi-threading for the first time and following along with HMH up to day 131 where Casey introduces the separate LowPriorityQueue for the FillGroundChunks.
Where I'm a bit lost is how the new low priority threads are getting kicked off? In the previous high priority queue (RenderQueue), PlatformCompleteAllWork() was called at the end to process the queue. For FillGroundChunks, the rendering doesn't process through TiledRenderGroupToOutput and so no complete all work is called.
I believe my understanding gap is around the complete all work. Does the infinite for loop in the threadproc keep the 2 low priority threads always spinning and when Addentry is called they just process? Is the complete all work function only there to ensure all work is completed before the next frame for rendering?
Thanks in advance,
Mebourne