-
Notifications
You must be signed in to change notification settings - Fork 900
oshmem: add some useless but inoffensive communications and see how o… #4734
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.
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
Conversation
12f4e2f
to
9a1ce25
Compare
@yosefe there might be. |
8955712
to
0252461
Compare
The IBM CI (GNU Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/e9c85b22d9b273bc0d4b9759fb6418fb |
The IBM CI (XL Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/6b75fe520b36c958476b22b25dd29344 |
0252461
to
82135c3
Compare
The IBM CI (GNU Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/2f9d6eecef186c3bc0f3d0b7c317e1a0 |
The IBM CI (XL Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/f236fa19ddd296534d4dd068413b4840 |
The IBM CI (PGI Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/6daefd4ce9d5b60a396f1175169af8b9 |
82135c3
to
74247bf
Compare
The IBM CI (GNU Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/cd479eee9d454e729dda217c396210cf |
The IBM CI (XL Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/7fcbddbc11d3bbc3422e12ad7b29d0fc |
74247bf
to
e5c7927
Compare
The IBM CI (GNU Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/1f3cd58761d8210f3d9079db09aec046 |
The IBM CI (XL Compiler) build failed! Please review the log, linked below. Gist: https://gist.github.com/ac8ee133e6dd2ca621ea5062cabf31cd |
e5c7927
to
a3324b3
Compare
…shmem+ucx handles that Signed-off-by: Gilles Gouaillardet <[email protected]>
instead of invoking ompi_request_test_all(), that will end up calling opal_progress() recursively, manually check the status of the requests. the same method is used in ompi_comm_request_progress() Refs open-mpi#3901 Signed-off-by: Gilles Gouaillardet <[email protected]>
a3324b3
to
680a070
Compare
@yosefe there is no problem with UCX nor SHMEM :-) |
…shmem+ucx handles that
Signed-off-by: Gilles Gouaillardet [email protected]