Lines Matching refs:barriers

35 <<synchronization-pipeline-barriers,Pipeline Barriers>>::
36     Pipeline barriers also provide synchronization control within a command
39     Pipeline barriers can: be used to control resource access within a
204 <<synchronization-image-memory-barriers,image memory barrier>>).
266 Layout transitions that are performed via image memory barriers execute in
279 of an <<synchronization-image-memory-barriers, image memory barrier>> is an
815 barriers.
1762 dependency, and for pipeline barriers all physical devices that are set in
2743 A <<synchronization-memory-barriers, memory barrier>> or other memory
5988 pipeline barriers, but split into two commands such that work between the
6018     flink:vkSetEvent, barriers in the [eq]##i##th element of
6022     For any element [eq]#i# of pname:pEvents, if barriers in the [eq]##i##th
6027     For any element [eq]#i# of pname:pEvents, if barriers in the [eq]##i##th
6146 each define a set of <<synchronization-memory-barriers, memory barriers>>.
6147 If no memory barriers are specified, then the first access scope includes no
6157 each define a set of <<synchronization-memory-barriers, memory barriers>>.
6158 If no memory barriers are specified, then the second access scope includes
6167 pipeline barriers, but split into two commands such that work between the
6244 [[synchronization-pipeline-barriers]]
6288 <<synchronization-pipeline-barriers-explicit-renderpass-tileimage, Tile
6350 flink:vkCmdPipelineBarrier2, except that the scopes and barriers are defined
6391 each define a set of <<synchronization-memory-barriers, memory barriers>>.
6392 If no memory barriers are specified, then the first access scope includes no
6402 each define a set of <<synchronization-memory-barriers, memory barriers>>.
6403 If no memory barriers are specified, then the second access scope includes
6480 [[synchronization-pipeline-barriers-explicit-renderpass-tileimage]]
6497 barriers since the start of the render pass instance.
6504 The following restrictions apply for such pipeline barriers:
6507   * The pipeline barriers can: only include memory barriers.
6508     That is, buffer memory barriers and image memory barriers must: not be
6521 [[synchronization-memory-barriers]]
6526 Memory barriers are used to <<synchronization-queue-transfers, transfer
6537 [[synchronization-global-memory-barriers]]
6540 Global memory barriers apply to memory accesses involving all memory objects
6630 [[synchronization-buffer-memory-barriers]]
6633 Buffer memory barriers only apply to memory accesses involving a specific
6638 Buffer memory barriers can: also be used to define a
6877 [[synchronization-image-memory-barriers]]
6880 Image memory barriers only apply to memory accesses involving a specific
6885 Image memory barriers can: also be used to define
7343 <<synchronization-buffer-memory-barriers, buffer memory barrier>> (for a
7344 buffer range) or an <<synchronization-image-memory-barriers, image memory
7361 <<synchronization-buffer-memory-barriers, buffer memory barrier>> (for a
7362 buffer range) or an <<synchronization-image-memory-barriers, image memory
7380 memory barriers used for release or acquire operations, respectively, they