Vulkan 1.4.361 Released With New NVIDIA Vendor Extension
([Vulkan] 4 Hours Ago
VK_NV_private_data_base_handle)
- Reference: 0001654969
- News link: https://www.phoronix.com/news/Vulkan-1.4.361
- Source link:
The Khronos Group is closing out the month of August with the Vulkan 1.4.361 specification update.
Collected over the past two weeks were various minor fixes and clarifications to the Vulkan API specification. There are improved VK_EXT_descriptor_heap align limits and other mostly maintenance updates/corrections. There is one new extension this time around and it's the NVIDIA VK_NV_private_data_base_handle.
The VK_NV_private_data_base_handle is used for obtaining the underlying Vulkan device handle when using the Vulkan API in a layered environment. If needing to communicate directly with the driver outside of the Vulkan layer chain, VK_NV_private_data_base_handle provides a pathway for doing so with there not being any other standardized option at the moment.
VK_NV_private_data_base_handle makes use of functionality the NVIDIA driver already has for being able to get the base device handle for the Vulkan device. For layers in this context, NVIDIA's motivation appears to be around like their Nsight graphics software. But this could have other use-cases as well in the growing ecosystem of different Vulkan layers.
More details on the Vulkan 1.4.361 driver changes can be found via [1]GitHub .
[1] https://github.com/KhronosGroup/Vulkan-Docs/commit/20a9e5892e2aab7b9776b16a238b10fc8133090a
Collected over the past two weeks were various minor fixes and clarifications to the Vulkan API specification. There are improved VK_EXT_descriptor_heap align limits and other mostly maintenance updates/corrections. There is one new extension this time around and it's the NVIDIA VK_NV_private_data_base_handle.
The VK_NV_private_data_base_handle is used for obtaining the underlying Vulkan device handle when using the Vulkan API in a layered environment. If needing to communicate directly with the driver outside of the Vulkan layer chain, VK_NV_private_data_base_handle provides a pathway for doing so with there not being any other standardized option at the moment.
VK_NV_private_data_base_handle makes use of functionality the NVIDIA driver already has for being able to get the base device handle for the Vulkan device. For layers in this context, NVIDIA's motivation appears to be around like their Nsight graphics software. But this could have other use-cases as well in the growing ecosystem of different Vulkan layers.
More details on the Vulkan 1.4.361 driver changes can be found via [1]GitHub .
[1] https://github.com/KhronosGroup/Vulkan-Docs/commit/20a9e5892e2aab7b9776b16a238b10fc8133090a