Vulkan 1.4.346 Released With Notable VK_KHR_device_address_commands
([Vulkan] 5 Hours Ago
VK_KHR_device_address_commands)
- Reference: 0001619305
- News link: https://www.phoronix.com/news/Vulkan-1.4.346-Released
- Source link:
Vulkan 1.4.346 was published today with one big new extension in tow: VK_KHR_device_address_commands.
The VK_KHR_device_address_commands extension is now public as a big addition worked on by the likes of AMD, Valve, NVIDIA, Collabora, Intel, LunarG, and others. It's a big one coming and allows for applications to use device addresses in place of buffer objects for most functionality.
VK_KHR_device_address_commands is intended to address a current Vulkan API limitation that applications / game engines end up currently needing to pass both buffer handles and device addresses. Since Vulkan 1.2 with VK_KHR_buffer_device_address there is the ability to obtain device addresses for buffers, but lots of functionality still depends upon buffer objects rather than device addresses. With VK_KHR_device_address_commands, that gap has been addressed. VK_KHR_device_address_commands adds new versions of older functions to be able to accept device addresses.
Since the publishing of Vulkan 1.4.346 overnight, there are already Mesa merge requests open for the [1]RADV driver and [2]Intel ANV driver for supporting VK_KHR_device_address_commands.
Besides this big new extension, Vulkan 1.4.346 brings other minor issue corrections too. All the details via [3]this Vulkan-Docs commit .
[1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40386
[2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40387
[3] https://github.com/KhronosGroup/Vulkan-Docs/commit/b71f0036e3f00fa0cda4d888a53f6081c62b4648
The VK_KHR_device_address_commands extension is now public as a big addition worked on by the likes of AMD, Valve, NVIDIA, Collabora, Intel, LunarG, and others. It's a big one coming and allows for applications to use device addresses in place of buffer objects for most functionality.
VK_KHR_device_address_commands is intended to address a current Vulkan API limitation that applications / game engines end up currently needing to pass both buffer handles and device addresses. Since Vulkan 1.2 with VK_KHR_buffer_device_address there is the ability to obtain device addresses for buffers, but lots of functionality still depends upon buffer objects rather than device addresses. With VK_KHR_device_address_commands, that gap has been addressed. VK_KHR_device_address_commands adds new versions of older functions to be able to accept device addresses.
Since the publishing of Vulkan 1.4.346 overnight, there are already Mesa merge requests open for the [1]RADV driver and [2]Intel ANV driver for supporting VK_KHR_device_address_commands.
Besides this big new extension, Vulkan 1.4.346 brings other minor issue corrections too. All the details via [3]this Vulkan-Docs commit .
[1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40386
[2] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/40387
[3] https://github.com/KhronosGroup/Vulkan-Docs/commit/b71f0036e3f00fa0cda4d888a53f6081c62b4648