Skip to content
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

Test MPI/CUDA polling in tasks instead of integrating with scheduler #1172

Open
msimberg opened this issue Jun 13, 2024 · 0 comments
Open

Test MPI/CUDA polling in tasks instead of integrating with scheduler #1172

msimberg opened this issue Jun 13, 2024 · 0 comments
Labels
category: senders/receivers P2300 effort: 3 A few days of work. effort: 4 A few weeks of work. priority: low Nice to have, but nobody is going to be sad if this is never done. type: cleanup type: refactoring

Comments

@msimberg
Copy link
Contributor

We should test if running the MPI/CUDA polling in standalone tasks works as well as integrating the polling in the scheduler. This would make the polling independent of the scheduler that it's running on and possibly make integration with other libraries easier. In addition it might make shutdown a bit simpler since we don't have to separately keep track of task counts, MPI request counts, and CUDA event counts; everything would fall under the task count. This might also make the polling slower. This also similar to what is proposed in ALPI.

@msimberg msimberg converted this from a draft issue Jun 13, 2024
@msimberg msimberg added effort: 3 A few days of work. effort: 4 A few weeks of work. priority: medium This should be done sooner or later. type: refactoring category: senders/receivers P2300 type: cleanup labels Jun 13, 2024
@msimberg msimberg added priority: low Nice to have, but nobody is going to be sad if this is never done. and removed priority: medium This should be done sooner or later. labels Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: senders/receivers P2300 effort: 3 A few days of work. effort: 4 A few weeks of work. priority: low Nice to have, but nobody is going to be sad if this is never done. type: cleanup type: refactoring
Projects
Status: Backlog
Development

No branches or pull requests

1 participant