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

Make examples in MPI_COMM_SPLIT_TYPE consistent with MPI_GET_HW_RESOURCE_INFO #823

Open
GuillaumeMercier opened this issue Dec 19, 2023 · 0 comments
Assignees
Labels
chap-contexts Groups, Contexts, Communicators, Caching Chapter Committee mpi-4.2 scheduled reading Reading is scheduled for the next meeting wg-hardware-topologies Hardware Topologies Working Group
Milestone

Comments

@GuillaumeMercier
Copy link

GuillaumeMercier commented Dec 19, 2023

Problem

The examples (7.3 and 7.4 pp 335-338) in MPI_COMM_SPLIT_TYPE (when using the GUIDED mode) does not use the URI format described in MPI_GET_HW_IRESOURCE_NFO.

Proposal

Change the text to have better consistency.

Changes to the Text

NUMANode -> hwloc://NUMANode

Impact on Implementations

None.

Impact on Users

None

References and Pull Requests

mpi-forum/mpi-standard/pull/955

@GuillaumeMercier GuillaumeMercier self-assigned this Dec 19, 2023
@GuillaumeMercier GuillaumeMercier added chap-contexts Groups, Contexts, Communicators, Caching Chapter Committee mpi-4.2 labels Dec 19, 2023
@GuillaumeMercier GuillaumeMercier added the wg-hardware-topologies Hardware Topologies Working Group label Jan 10, 2024
@wesbland wesbland added the scheduled reading Reading is scheduled for the next meeting label Mar 4, 2024
@wesbland wesbland added this to the March 2024 milestone Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chap-contexts Groups, Contexts, Communicators, Caching Chapter Committee mpi-4.2 scheduled reading Reading is scheduled for the next meeting wg-hardware-topologies Hardware Topologies Working Group
Projects
Status: To Do
Development

No branches or pull requests

2 participants