Only need objects created when mapping, otherwise can be deferred until first use on the queue thread.
Thinking:
- context has a single platform context for resource stuff (this is the 'root' share group context)
- queues have a context of their own
- swap chains have a context of their own
The context could then have a small thread that listens for requests to map/unmap buffers and delete objects, and creations happen delayed on first execution.
Only need objects created when mapping, otherwise can be deferred until first use on the queue thread.
Thinking:
The context could then have a small thread that listens for requests to map/unmap buffers and delete objects, and creations happen delayed on first execution.