VK_EXT_descriptor_heap(3) Manual Page

136

1

Ratified

VK_EXT_descriptor_heap

This extension allows explicit management of descriptors, and the memory used to store descriptors, conceptualised as descriptor heaps. Descriptor heap memory can be accessed as any other memory, enabling management of descriptors on both CPU and the GPU.

This extension was developed based on issues discovered with VK_EXT_descriptor_buffer. There are more constraints on how it is implemented, to provide more portable guarantees and more predictable performance characteristics. For instance, rather than an arbitrary number of sampler or resource buffers, there is exactly one sampler heap and exactly one resource heap.

This extension also eliminates descriptor sets and pipeline layouts completely; instead applications can look descriptors up solely by their offset into a heap. Shaders still using descriptor set and binding decorations can still be mapped to heaps through an API that maps set and binding decorations to heap offsets, either as constants or through push data. This new mapping API also enables a much more straightforward mapping to HLSL shaders using the root signature and descriptor table interfaces.

The push constant API has also been replaced with the push data interface, which aims to provide much more clarity about how data is passed to the shader, without requiring any mapping information to be provided during pipeline or shader creation. Mappings are still available for shaders written for the legacy interface.

There is also a much clearer path for mapping shader constant data, with two recommended options for mapping constant data through push data; either directly in push data, or through a device address stored in push data, both of which can be mapped to shaders with set and binding interfaces.

If VK_ARM_tensors is supported:

If VK_EXT_custom_border_color is supported:

If VK_ARM_tensors is supported:

If VK_EXT_custom_border_color is supported:

If VK_EXT_fragment_density_map is supported:

If VK_NV_device_generated_commands is supported:

If VK_ARM_tensors is supported:

If VK_EXT_custom_border_color is supported:

If VK_EXT_device_generated_commands is supported:

If VK_EXT_fragment_density_map is supported:

If VK_EXT_shader_object is supported:

If VK_KHR_ray_tracing_pipeline or VK_NV_ray_tracing is supported:

If VK_NV_device_generated_commands is supported:

No cross-references are available

For more information, see the Vulkan Specification.

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.

Copyright 2014-2026 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0