Media/compute-runtime
1
0
Fork 0
mirror of https://github.com/intel/compute-runtime.git synced 2025-09-15 13:01:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

documentation: fix several typos in imm cmdlist description

Browse Source 
Signed-off-by: Naklicki, Mateusz <mateusz.naklicki@intel.com>
This commit is contained in:
Naklicki, Mateusz
2024-11-04 15:18:49 +00:00
committed by Compute-Runtime-Automation
parent e3acd850ea
commit bccd26413b
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
programmers-guide/IMMEDIATE_COMMANDLIST.md
View File

@ -6,7 +6,7 @@ SPDX-License-Identifier: MIT
-->
# Level Zero Immediate Command list
# Level Zero Immediate Command Lists
* [Introduction](#Introduction)
* [Availability](#Availability)
@ -17,7 +17,7 @@ SPDX-License-Identifier: MIT
# Introduction
Immediate command lists is a feature provided by Level-Zero specification to allow for very low latency submission usage models. In this scheme, commands appended on the command list such as launching a kernel or performing a memory copy are immediately submitted to the device for execution. This is different from a regular command list where multiple commands can be stitched and submitted together for execution .
Immediate command lists is a feature provided by Level-Zero specification to allow for very low latency submission usage models. In this scheme, commands appended on the command list such as launching a kernel or performing a memory copy are immediately submitted to the device for execution. This is different from a regular command list where multiple commands can be stitched and submitted together for execution.
Distinctions between an immediate command list compared to a regular command list include (but not limited to) the following:
@ -26,7 +26,7 @@ Distinctions between an immediate command list compared to a regular command lis
* Immediate command lists are not required to be closed or reset.
* Synchronization of immediate command lists cannot be performed by user via zeCommandQueueSynchronize as the user will not have a command queue handle or via a fence handle as fences are associated with a command queue. Proper synchronization models are detailed further below.
Since the intention of immediate command lists are to primarily provide a razor thin submission interface to the device, they are well suited to be used in workloads who have tendency to launch small or short running kernels and also need to run multiple iterations of such kernels. Examples of workloads with such characteristics can be found in HPC environments and also ML/DL frameworks.
Since the intention of immediate command lists are to primarily provide a razor thin submission interface to the device, they are well suited to be used in workloads that have tendency to launch small or short running kernels and also need to run multiple iterations of such kernels. Examples of workloads with such characteristics can be found in HPC environments and also ML/DL frameworks.
## Programming model
@ -62,7 +62,7 @@ Performing copies:
1,
&events[0]);
zeEventHostSynchronize(events[1], std::numeric_limits<uint64_t>::max() - 1));
zeEventHostSynchronize(events[1], std::numeric_limits<uint64_t>::max() - 1);
```
Pseudo-code for creating immediate command list (sync mode):
@ -108,4 +108,4 @@ For more code samples, please refer [compute-benchmarks](https://github.com/inte
# References
* https://one-api.gitlab-pages.devtools.intel.com/level_zero/core/PROG.html#low-latency-immediate-command-lists
* https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/PROG.html#low-latency-immediate-command-lists