[Question] Documentation missing: migrating OpenCL profiling code to Level Zero"

Open
#66 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
api, documentation

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.

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

Dominant language
C++
Stars
335
Forks
140
Avg merge
12h 32m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oneapi-src/level-zero

All issues in oneapi-src/level-zero

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.