Skip to content

[SYCL] Use copy engine for memory read/write operations #6783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

asudarsa
Copy link
Contributor

In the present state of the L0 plugin, MemBufferWrite and MemBufferRead operations are being executed using compute engines. This patch changes this behavior for the operations to be executed using copy engines.
It is expected to improve performance.

Thanks

Signed-off-by: Arvind Sudarsanam [email protected]

@asudarsa asudarsa requested a review from a team as a code owner September 14, 2022 16:02
@asudarsa
Copy link
Contributor Author

asudarsa commented Sep 14, 2022

The following failures are seen in other PRs as well:
Failed Tests (5):
SYCL :: dword_atomic_smoke.cpp
SYCL :: lsc/lsc_fence.cpp
SYCL :: lsc/lsc_slm.cpp
SYCL :: lsc/lsc_surf.cpp
SYCL :: lsc/lsc_usm.cpp

Do we need a Jira for it? I can create one if needed.
@kbobrovs, can you please comment if convenient?

Thanks

@bader bader merged commit 65c3ea2 into intel:sycl Sep 15, 2022
@asudarsa asudarsa deleted the asudarsa/use_copy_engine_for_memread_memwrite branch September 24, 2022 20:21
smaslov-intel added a commit that referenced this pull request Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants