@@ -821,11 +821,6 @@ Execution
821821- Command queue submission is free-threaded, allowing multiple Host threads to share the same command queue.
822822- If multiple Host threads enter the same command queue simultaneously, then execution order is undefined.
823823- Command lists can only be executed on a command queue with an identical command queue group ordinal.
824- - If a device contains multiple sub-devices, then command lists submitted to a device-level command queue
825- may be optimized by the driver to fully exploit the concurrency of the sub-devices by distributing command lists across sub-devices.
826- - If the application prefers to opt-out of these optimizations, such as when the application plans to perform this distribution itself,
827- then it should use ${X}_COMMAND_QUEUE_FLAG_EXPLICIT_ONLY. Only command lists created using ${X}_COMMAND_LIST_FLAG_EXPLICIT_ONLY
828- can be executed on a command queue created using ${X}_COMMAND_QUEUE_FLAG_EXPLICIT_ONLY.
829824
830825
831826Destruction
@@ -869,11 +864,6 @@ Appending
869864- For usage-models where maximum throughput is desired, applications should
870865 use ${X}_COMMAND_LIST_FLAG_MAXIMIZE_THROUGHPUT. This flag will indicate to the driver
871866 it may perform additional device-specific optimizations.
872- - If a device contains multiple sub-devices, then commands submitted to a device-level
873- command list may be optimized by the driver to fully exploit the concurrency of the
874- sub-devices by distributing commands across sub-devices. If the application prefers
875- to opt-out of these optimizations, such as when the application plans to perform this
876- distribution itself, then it should use ${X}_COMMAND_LIST_FLAG_EXPLICIT_ONLY.
877867
878868The following pseudo-code demonstrates a basic sequence for creation of command lists:
879869
0 commit comments