Missing support for asynchronous copying using CUDA_MEMCPY2D and CUDA_MEMCPY3D_PEER parameters #688
Labels
Comments
eyalroz
added a commit
that referenced
this issue
Oct 21, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures
eyalroz
added a commit
that referenced
this issue
Oct 26, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures
eyalroz
added a commit
that referenced
this issue
Oct 26, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures
eyalroz
added a commit
that referenced
this issue
Oct 28, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures
eyalroz
added a commit
that referenced
this issue
Nov 15, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures * Explicitly including `memory.hpp` in `multi_wrapper_impls/memory.hpp`
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
* All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures * Explicitly including `memory.hpp` in `multi_wrapper_impls/memory.hpp`
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
…opy functions: * All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures * Explicitly including `memory.hpp` in `multi_wrapper_impls/memory.hpp`
eyalroz
added a commit
that referenced
this issue
Nov 16, 2024
…opy functions: * All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures * Explicitly including `memory.hpp` in `multi_wrapper_impls/memory.hpp`
eyalroz
added a commit
that referenced
this issue
Nov 17, 2024
…opy functions: * All copy functions now take an optional stream via an `optional_ref` parameter; * No longer using the `cuda::memory::async` subnamespace for any copy functions; they are all directly in `cuda::memory` * Fixes #688: Now supporting async copy using copy parameters structures * Explicitly including `memory.hpp` in `multi_wrapper_impls/memory.hpp`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently support copying using the comprehensive copy parameter structures, for 2D and for 3D, but - we do not support such scheduling such copies on streams. Let's add that support.
The text was updated successfully, but these errors were encountered: