Skip to content

AtoU page 60-61 border: this reads as a deprecation without a deprecation #964

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

Open
Tracked by #911
wrwilliams opened this issue Mar 5, 2025 · 0 comments
Open
Tracked by #911
Labels
chap-p2p Point to Point Communication Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard wg-p2p Point-to-Point Working Group

Comments

@wrwilliams
Copy link

wrwilliams commented Mar 5, 2025

Advice to Users: The use of a global shared buffer can be problematic when used for communication in different libraries, as the buffer represents a shared resource used for all buffered mode communication. Further, with the introduction of the Sessions Model, the use of a single shared buffer violates the concept of resource isolation that is intended with MPI Sessions. It is therefore recommended, especially for libraries and programs using the Sessions Model, to use only communicator-specific or session- specific buffers. (End of advice to users.)

@wesbland wesbland added the mpi-6 For inclusion in the MPI 5.1 or 6.0 standard label Mar 5, 2025
@github-project-automation github-project-automation bot moved this to To Do in MPI Next Mar 5, 2025
@wesbland wesbland added wg-p2p Point-to-Point Working Group chap-p2p Point to Point Communication Chapter Committee labels Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chap-p2p Point to Point Communication Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard wg-p2p Point-to-Point Working Group
Projects
Status: To Do
Development

No branches or pull requests

2 participants