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

Feedback on MPI Needs ABI Article #3

Open
mmccarty opened this issue Aug 17, 2021 · 0 comments
Open

Feedback on MPI Needs ABI Article #3

mmccarty opened this issue Aug 17, 2021 · 0 comments

Comments

@mmccarty
Copy link

  1. typo

Finally, if I link my application against against a specific MPI implemntation, I must run the resulting application with a compatible mpirun.

  1. See mpi4py CI pipelines for more nasty examples like Rust MPI.

  2. Love this point!

The question is whether the MPI user community cares more about these 100 nanoseconds versus the hours and days it takes humans to build the MPI software ecosystem twice, three times, or more, because of the lack of a standard ABI.

I think this is a key point that you should amplify. Basically, the trade off in developer productivity versus performance.

Great article! I hope this happens!

jeffhammond added a commit that referenced this issue Aug 20, 2021
address #3 part 1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant