Lines Matching refs:dependency
59 synchronization scopes will not be included in the resulting dependency.
63 pipeline stages to be excluded from a dependency.
79 execution dependency *E* between *A'* and *B'*.
80 * Execution dependency *E* guarantees that *A'* happens-before *B'*.
83 An _execution dependency chain_ is a sequence of execution dependencies that
84 form a happens-before relation between the first dependency's *A'* and the
85 final dependency's *B'*.
87 intersection of *B~S~* in the first dependency and *A~S~* in the second
88 dependency is not an empty set.
89 The formation of a single execution dependency from an execution dependency
94 dependency chain.
128 A _memory dependency_ is an execution dependency which includes availability
137 Most synchronization commands in Vulkan define a memory dependency.
141 by the _access scopes_ of a memory dependency.
142 Any type of access that is in a memory dependency's first access scope and
144 Any type of access that is in a memory dependency's second access scope and
147 scopes will not be included in the resulting dependency.
149 A memory dependency enforces availability and visibility of memory accesses
152 execution dependency chains>>:
161 a memory dependency *m* between *A'* and *B'*.
162 * Memory dependency *m* guarantees that:
172 Write-after-read hazards can be solved with just an execution dependency,
185 memory dependency>> (e.g. by using an
187 When a layout transition is specified in a memory dependency, it
188 happens-after the availability operations in the memory dependency, and
237 In effect there is an implicit execution dependency from each such layout
289 <<synchronization-dependencies-chains, dependency chain>>.
297 execution dependency.
977 a memory dependency.
1270 …'Bitmask specifying memory access types that will participate in a memory dependency',type='enums']
1655 For these pipeline stages, an execution or memory dependency from the first
1657 _framebuffer-global_ dependency, or split into multiple _framebuffer-local_
1659 A dependency with non-framebuffer-space pipeline stages is neither
1678 framebuffer-local dependency include only the operations performed within
1681 framebuffer-local dependency.
1684 framebuffer-global dependency include operations on all framebuffer-regions.
1694 In other words, it is a pixel granularity dependency.
1698 pixel granularity dependency.
1710 In other words, it is a sample granularity dependency.
1714 granularity dependency.
1729 Practically, the pixel vs sample granularity dependency means that if an
1736 fragment operations happen-after a framebuffer-local dependency for each
1743 a framebuffer-global dependency is required.
1752 framebuffer-global dependency is specified for those stages.
1764 a dependency.
1765 Including a framebuffer-global dependency in your rendering will usually
1778 A view-local dependency only includes operations from a single
1783 A view-global dependency includes all views in the view mask of the source
1791 dependency is specified.
1800 A device-local dependency acts as multiple separate dependencies, one for
1802 dependency only includes operations from that physical device in both
1804 A non-device-local dependency is a single dependency where both
1809 dependency, and for pipeline barriers all physical devices that are set in
1810 the command buffer's current device mask participate in the dependency.
1814 non-device-local dependency for that synchronization command.
1821 one physical device that performs the dependency.
1963 unless those queue submissions have some dependency which ensures that they
1982 dependency from a queue to the host.
2411 dependency on the batches that were submitted as part of that command, and
2492 An execution dependency is defined by waiting for a fence to become
2508 of a memory dependency defined by a fence only includes device access.
2510 dependency must: be used to guarantee this.
2920 dependency
3478 dependency on the batch, and defines _semaphore signal operations_ which set
3521 memory dependency between prior semaphore signal operations and the batch,
3532 a memory dependency with a semaphore wait operation if the value the
3569 the execution dependency, and happens-before the second set of operations in
3570 the execution dependency.
3621 This barrier accomplishes a dependency chain between previous presentation
3623 layout transition performed in between, and does not introduce a dependency
3630 dependency from that same stage to itself with the layout transition
4017 execution dependency chain that, when complete, leads to objects being
4446 fine-grained dependency between commands submitted to the same queue, or
4448 Events must: not be used to insert a dependency between commands submitted
4648 There must: be an execution dependency between fname:vkResetEvent and
4653 There must: be an execution dependency between fname:vkResetEvent and
4687 A memory dependency is defined between the event signal operation and
4722 With flink:vkCmdSetEvent, the full dependency information is not known until
4729 event signal operation occurs, and no dependency is generated.
4760 [open,refpage='VkDependencyInfoKHR',desc='Structure specifying dependency information for a synchro…
4794 <<synchronization-dependencies-memory, memory dependency>>.
4824 dependency on commands that were submitted before it, and defines an event
4839 signal operation occurs, and no execution dependency is generated.
4876 execution dependency on commands that were submitted before it, and defines
4891 no effect, no event unsignal operation occurs, and no execution dependency
4904 There must: be an execution dependency between fname:vkCmdResetEvent2KHR
4908 There must: be an execution dependency between fname:vkCmdResetEvent2KHR
4943 dependency on commands that were submitted before it, and defines an event
4958 event unsignal operation occurs, and no execution dependency is generated.
4968 There must: be an execution dependency between fname:vkCmdResetEvent and
4973 There must: be an execution dependency between fname:vkCmdResetEvent and
5014 dependency defined by any element [eq]#i# of pname:pDependencyInfos are
5033 memory dependency defined by any element [eq]#i# of pname:pDependencyInfos
5042 memory dependency between two sets of action commands, roughly in the same
5053 Another execution dependency (e.g. a pipeline barrier or semaphore with
5160 Since flink:vkCmdSetEvent does not have any dependency information beyond a
5170 dependency between prior event signal operations on the same queue or the
5223 dependency between two sets of action commands, roughly in the same way as
5239 Another execution dependency (e.g. a pipeline barrier or semaphore with
5287 [open,refpage='vkCmdPipelineBarrier2KHR',desc='Insert a memory dependency',type='protos']
5306 dependency defined by any element [eq]#i# of pname:pDependencyInfos are
5312 memory dependency defined by any element [eq]#i# of pname:pDependencyInfos
5345 [open,refpage='vkCmdPipelineBarrier',desc='Insert a memory dependency',type='protos']
5383 dependency between commands that were submitted before it, and those
5435 any dependency between <<synchronization-framebuffer-regions,
5484 === Subpass Self-dependency
5502 That is, there must: exist a subpass dependency with pname:srcSubpass and
5504 More than one self-dependency can: be declared for each subpass.
5533 If the self-dependency has ename:VK_DEPENDENCY_BY_REGION_BIT
5559 dependency that is created by a synchronization command that includes them.
5594 dependency>> affecting all device memory.
5654 That is, a memory dependency formed from a buffer memory barrier is
5699 dependency>> limited to a range of a buffer, and can: define a
5864 That is, a memory dependency formed from an image memory barrier is
5909 dependency>> limited to an image subresource range, and can: define a
6211 by defining an execution dependency between them, e.g. using a semaphore.
6351 dependency with prior host operations, and execution of command buffers