Repository navigation
Conversation
|
On ivys2/3, with CUDA 9.1, r396.21 |
|
@e-ago I only modified gds_kernel_loopback_latency. |
…pu. add atomic helpers
…ile --size=0 launches a void kernel. Implement !peersync case in terms of CUDA stream callbacks, relies on CPU posting descriptors via gds_post_descriptors(). use NVTX macros in stream callback.
|
just verified that gds_kernel_loopback_latency works on each individual machine |
|
also in !peersync (-P) mode |
|
confirming that gds_kernel_latency works in peersync mode: |
|
running gds_kernel_latency works in !peersync mode over the following branches:
FAIL=stuck after pre-submisison, top shows user-mode process taking 100% of CPU core |
|
bisecting: |
|
rewriting new_memops branch to fix the compile breakages earlier |
|
bisected the !peersync problem, it is due to: |
|
filed issue #64 to track future work |
|
@e-ago you should use gds_kernel_loopback_latency to test the feature added by this PR |
|
Tested again on ivys, I can confirm that:
On the master branch, gds_kernel_latency passes all tests. |
that is because on gds_kernel_latency really !peersync was basically a no-op. |
These changes help evaluating the relative performance of the direct Async (GPU->NIC) vs offloaded (GPU->CPU->NIC) path.