You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
The text was updated successfully, but these errors were encountered: