oneapi-src / oneapi-src/level-zero
[Question] Documentation missing: migrating OpenCL profiling code to Level Zero"
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Description
Hi all,
I wonder if there is any call in LevelZero API equivalent to clGetEventProfilingInfo from OpenCL:
https://www.khronos.org/registry/OpenCL/sdk/2.1/docs/man/xhtml/clGetEventProfilingInfo.html
What I would like to do is to measure the data transfer time (zeCommandListAppendMemoryCopy, Host -> Device and Device->Host. Is there any functionality in level zero to do so?
I saw the kernel timers use a different function zeCommandListAppendQueryKernelTimestamps but I can't find the equivalent for data transfers.
Any pointers/examples will appreciate it.
Thank you,
Juan
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Level Zero API entry points named in the issue: zeCommandListAppendMemoryCopy and zeCommandListAppendQueryKernelTimestamps, and compare them with OpenCL's clGetEventProfilingInfo. Done means documenting whether data-transfer timing is supported and providing a relevant example or pointer for Host-to-Device and Device-to-Host copies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100