Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use async cuMemcpy APIs instead of synchronous ones #311

Closed
kkraus14 opened this issue Oct 31, 2023 · 0 comments · Fixed by #374
Closed

Use async cuMemcpy APIs instead of synchronous ones #311

kkraus14 opened this issue Oct 31, 2023 · 0 comments · Fixed by #374

Comments

@kkraus14
Copy link

https://github.com/rapidsai/kvikio/blob/branch-23.12/cpp/include/kvikio/posix_io.hpp#L179-L185

Currently, it looks like synchronous cuMemcpy APIs are being used which effectively synchronize the entire device. If someone is using streams explicitly or is using multiple threads with per thread default stream, this will cause unnecessary synchronization.

Instead, we should probably move to using the async cuMemcpy APIs and then synchronizing the stream explicitly
@madsbk madsbk mentioned this issue Apr 29, 2024
Merged
@rapids-bot rapids-bot bot closed this as completed in #374 May 7, 2024
rapids-bot bot pushed a commit that referenced this issue May 7, 2024
@madsbk
POSIX IO: use async memcpy (#374)
8081fbb 
Closes #311

Authors:
  - Mads R. B. Kristensen (https://github.com/madsbk)

Approvers:
  - Vukasin Milovanovic (https://github.com/vuule)

URL: #374
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

POSIX IO: use async memcpy madsbk/kvikio
1 participant
@kkraus14