nvshmem wait_until parameter is signal_op then signal_val.
but here in nvshmem4py, the parameter is signal_val then signal_op
Thank you for the bug report. I will create an internal bug for tracking and look into it.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Potential NVSHMEM allocated memory performance issue | 19 | 1486 | May 10, 2024 | |
| NVSHMEM issues with synchronization | 5 | 762 | July 18, 2023 | |
| How to run nvshmemx_uint64_wait_until_on_stream concurrently? | 1 | 269 | April 8, 2024 | |
| NVSHMEM isuues with nvshmem_TYPENAME_put | 6 | 614 | November 21, 2023 | |
| BUG: call cudaFree(0) before nvshmem_init() makes nvshmem_barrier_all() fails | 6 | 98 | April 19, 2025 | |
| [nvshmem4py] nvshmem.core.finalize() does not handle everything | 6 | 77 | July 7, 2025 | |
| Using Atomic Device Intrinsics over Volatile | 1 | 48 | January 4, 2025 | |
| Nvshmem fails to finalize | 4 | 1107 | January 16, 2024 | |
| Raise error when link nvshmem in my application | 13 | 1503 | January 2, 2024 | |
| Nvshmem4py Buffer can not be freed by python lifetime | 4 | 55 | July 6, 2025 |