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

Querying runtime support level #10

Open
sherief opened this issue Apr 2, 2022 · 2 comments
Open

Querying runtime support level #10

sherief opened this issue Apr 2, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@sherief
Copy link

sherief commented Apr 2, 2022

When deploying apps and getting telemetry, it's critical to be able to "query the caps" of the DirectStorage queue and file once created. Are the telemetry numbers from a fast path of NVMe PCIe 4.0 to vidmem, or is this NVMe to sysmem to vidmem? Or is this even an hdd with DirectStorage as a compat layer? There's no way to tell in the current API.

@damyanp
Copy link
Member

damyanp commented Apr 4, 2022

Am I right in understanding that the request here is that you want to be able to gather some metrics from DirectStorage so that in telemetry that your game is recording you can find out whether DirectStorage is using the mapping layer or not?

Note that there is no direct fast path from NVMe to vram yet, it always goes via system memory first. We're planning to enable the direct fast path in a future release.

@damyanp damyanp added the enhancement New feature or request label Apr 4, 2022
@sherief
Copy link
Author

sherief commented Apr 5, 2022

Correct, my intention is to know what level of hardware support am I getting - if I can get more info than the mapping layer I'd be happy. Excited for future releases! :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants