mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-26 04:55:12 +00:00
22a5a1459f
* Update release number to 124.
Github Issues:
* Fix Makefile SPECREMARK macro to work when not building in a git tree
(public issue 992).
* Ignore pname:aspectMask for unused attachments in
slink:VkSubpassDescription2KHR valid usage statements (public pull
request 1028).
* Minor markup / spelling fixes (public pull requests 1035, 1045).
Internal Issues:
* Fix markup in Valid Usage statement for slink:VkCreateFramebuffer
(internal issue 1823).
* Add a new <<synchronization-signal-operation-order, _signal operation
order_>> section to the synchronization chapter which describes in
detail the ordering guarantees provided by the API between fence and
semaphore signal operations (internal merge request 3368).
* Move generated `appendix/meta/` files into the Makefile GENERATED
directory (internal merge request 3381).
New Extensions
* `<<VK_KHR_shader_clock>>`
* `<<VK_KHR_timeline_semaphore>>`
113 lines
3.8 KiB
Plaintext
113 lines
3.8 KiB
Plaintext
include::{generated}/meta/VK_EXT_inline_uniform_block.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2018-08-01
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Daniel Rakos, AMD
|
|
- Jeff Bolz, NVIDIA
|
|
- Slawomir Grajewski, Intel
|
|
- Neil Henning, Codeplay
|
|
|
|
This extension introduces the ability to back uniform blocks directly with
|
|
descriptor sets by storing inline uniform data within descriptor pool
|
|
storage.
|
|
Compared to push constants this new construct allows uniform data to be
|
|
reused across multiple disjoint sets of draw or dispatch commands and may:
|
|
enable uniform data to be accessed with less indirections compared to
|
|
uniforms backed by buffer memory.
|
|
|
|
=== New Object Types
|
|
|
|
None
|
|
|
|
=== New Enum Constants
|
|
|
|
* Extending elink:VkStructureType:
|
|
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_INLINE_UNIFORM_BLOCK_FEATURES_EXT
|
|
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_INLINE_UNIFORM_BLOCK_PROPERTIES_EXT
|
|
** ename:VK_STRUCTURE_TYPE_WRITE_DESCRIPTOR_SET_INLINE_UNIFORM_BLOCK_EXT
|
|
** ename:VK_STRUCTURE_TYPE_DESCRIPTOR_POOL_INLINE_UNIFORM_BLOCK_CREATE_INFO_EXT
|
|
|
|
* Extending elink:VkDescriptorType:
|
|
** ename:VK_DESCRIPTOR_TYPE_INLINE_UNIFORM_BLOCK_EXT
|
|
|
|
=== New Enums
|
|
|
|
None
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkPhysicalDeviceInlineUniformBlockFeaturesEXT
|
|
* slink:VkPhysicalDeviceInlineUniformBlockPropertiesEXT
|
|
* slink:VkWriteDescriptorSetInlineUniformBlockEXT
|
|
* slink:VkDescriptorPoolInlineUniformBlockCreateInfoEXT
|
|
|
|
=== New Functions
|
|
|
|
None
|
|
|
|
=== New Built-In Variables
|
|
|
|
None
|
|
|
|
=== Issues
|
|
|
|
1) Do we need a new storage class for inline uniform blocks vs uniform
|
|
blocks?
|
|
|
|
*RESOLVED*: No.
|
|
The code:Uniform storage class is used to allow the same syntax used for
|
|
both uniform buffers and inline uniform blocks.
|
|
|
|
2) Is the descriptor array index and array size expressed in terms of bytes
|
|
or dwords for inline uniform block descriptors?
|
|
|
|
*RESOLVED*: In bytes, but both must: be a multiple of 4, similar to how push
|
|
constant ranges are specified.
|
|
The pname:descriptorCount of sname:VkDescriptorSetLayoutBinding thus
|
|
provides the total number of bytes a particular binding with an inline
|
|
uniform block descriptor type can hold, while the pname:srcArrayElement,
|
|
pname:dstArrayElement, and pname:descriptorCount members of
|
|
sname:VkWriteDescriptorSet, sname:VkCopyDescriptorSet, and
|
|
sname:VkDescriptorUpdateTemplateEntry (where applicable) specify the byte
|
|
offset and number of bytes to write/copy to the binding's backing store.
|
|
Additionally, the pname:stride member of
|
|
sname:VkDescriptorUpdateTemplateEntry is ignored for inline uniform blocks
|
|
and a default value of one is used, meaning that the data to update inline
|
|
uniform block bindings with must be contiguous in memory.
|
|
|
|
3) What layout rules apply for uniform blocks corresponding to inline
|
|
constants?
|
|
|
|
*RESOLVED*: They use the same layout rules as uniform buffers.
|
|
|
|
4) Do we need to add non-uniform indexing features/properties as introduced
|
|
by `VK_EXT_descriptor_indexing` for inline uniform blocks?
|
|
|
|
*RESOLVED*: No, because inline uniform blocks are not allowed to be
|
|
"`arrayed`".
|
|
A single binding with an inline uniform block descriptor type corresponds to
|
|
a single uniform block instance and the array indices inside that binding
|
|
refer to individual offsets within the uniform block (see issue #2).
|
|
However, this extension does introduce new features/properties about the
|
|
level of support for update-after-bind inline uniform blocks.
|
|
|
|
5) Is the pname:descriptorBindingVariableDescriptorCount feature introduced
|
|
by `VK_EXT_descriptor_indexing` supported for inline uniform blocks?
|
|
|
|
*RESOLVED*: Yes, as long as other inline uniform block specific limits are
|
|
respected.
|
|
|
|
6) Do the robustness guarantees of pname:robustBufferAccess apply to inline
|
|
uniform block accesses?
|
|
|
|
*RESOLVED*: No, similarly to push constants, as they are not backed by
|
|
buffer memory like uniform buffers.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2018-08-01 (Daniel Rakos)
|
|
- Internal revisions
|