Jump to content
  • Advertisement

DX12 Async Compute Descriptor Heaps

Recommended Posts

Posted (edited)

I'm reworking my descriptor heap strategy, so I'm digging through everything again.  On nVidia's DirectX 12 Do's and Don'ts page, they say:

  • Make sure to use just one CBV/SRV/UAV/descriptor heap as a ring-buffer for all frames if you want to aim at running parallel asynchronous compute and graphics workloads

I was under the impression that calling SetDescriptorHeaps could cause a flush.  Am I to understand that if all frames use the same descriptor heap, there won't be a flush, and the compute work can continue to access the descriptors despite newer graphics command lists calling SetDescriptorHeaps?

Does anyone have any additional information about managing memory to support async Compute?

Edited by Funkymunky

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!