Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print VK_EXT_memory_budget stats on allocation failure #1112

Closed

Conversation

liam-middlebrook
Copy link
Contributor

@liam-middlebrook liam-middlebrook commented Jul 2, 2019

This should help with logging efforts for #1100 .

When an allocation fails right now DXVK will print out the following
statistics for each heap:
 allocated - Memory allocated by DXVK in MB
 used      - Memory used by DXVK (from the chunk that it has allocated) in MB
 available - Size of the heap in MB

This change re-works this logging to include values provided by the
VK_EXT_memory_budget extension, providing the following additional
information:
 allocated (driver) - Memory allocated in MB as reported by the driver
     - VK_EXT_memory_budget's `heapUsage`
 available (driver) - Memory available for usage by the application as
                      reported by the driver
     - VK_EXT_memory_budget's `heapBudget`
Restore logging to the behavior before the
"[dxvk] Print memory_budget stats on allocation failure"
commit, if VK_EXT_memory_budget support isn't advertised by the driver.
@liam-middlebrook
Copy link
Contributor Author

Let me know if you'd like me to fixup the second into the first.

doitsujin added a commit that referenced this pull request Jul 3, 2019
Based on PR #1112, but using a cleaner method to check
support for the VK_EXT_memory_budget extension.

Suggested-by: Liam Middlebrook <lmiddlebrook@nvidia.com>
@doitsujin
Copy link
Owner

Thanks; I added a cleaner way to check whether the DxvkDevice supports VK_EXT_memory_budget and added the logging stuff based on that.

@doitsujin doitsujin closed this Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants