libcudacxx
libcudacxx copied to clipboard
NVIDIA
Draft: Document asynchronous threads
Let’s wait for Dan’s feedback since I’m not sure at all about this one. Just opened a new PR because the old one got quite out of sync with respect to the latest changes in the repo.
From: Michael Schellenberger Costa @.> Sent: Tuesday, February 21, 2023 11:53:04 AM To: NVIDIA/libcudacxx @.> Cc: Gonzalo Brito @.>; Author @.> Subject: Re: [NVIDIA/libcudacxx] Document asynchronous threads (PR #371)
@miscco approved this pull request.
— Reply to this email directly, view it on GitHubhttps://github.com/NVIDIA/libcudacxx/pull/371#pullrequestreview-1307175216, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APQD346SCWXMT27SJVJVVZDWYSNBBANCNFSM6AAAAAAVC3TJL4. You are receiving this because you authored the thread.Message ID: @.***>
NVIDIA GmbH Wuerselen Amtsgericht Aachen HRB 8361 Managing Directors: Michael Ching, Donald Robertson, Rebecca Peters and Ludwig von Reiche
This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Initiation of an async-operation (memcpy_async) is not required to spawn a new async-thread. It synchronizes-with an async-thread (could spawn) which is responsible for eventual completion of the async-operation.
