Use Cases Chapter #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SteVwonder
commented
Sep 29, 2020
pmix-standard.bib
Outdated
Comment on lines
63
to
70
| @misc{ompix-moc, | ||
| } | ||
|
|
||
| @inproceedings{2016:Hamidouche, | ||
| } | ||
|
|
||
| @inproceedings{2018:Vallee, | ||
| } |
There was a problem hiding this comment.
TODO: I still need to convert these references over to bibtex.
Chap_Use_Cases.tex
Outdated
|
|
||
| After calling \refapi{PMIx_Commit} a process can activate the Business Card Exchange collective operation by calling \refapi{PMIx_Fence}. The \refapi{PMIx_Fence} operation is collective over the set of processes specified in the argument set. That allows for the collective to span a subset of a namespace or multiple namespaces. After the completion of the \refapi{PMIx_Fence} operation, the data \refapi{PMIx_Put} by other processes is available to the local process through a call to \refapi{PMIx_Get} which returns the key/value pairs necessary to establish the connection(s) with the other processes. | ||
|
|
||
| The \refapi{PMIx_Fence} operation must have a "Synchronize Only" mode that works as a barrier operation. This is helpful if the communication library requires a synchronization before leaving initialization or starting finalization, for example. |
There was a problem hiding this comment.
Looks like quite a few places where " needs to be replaced with `` and ''.
|
I noticed there are also several broken references to attributes. They could be due to differences between the RFCs and the standard. They could also just be something simple like copy-paste errors. We need to dig further. |
SteVwonder
force-pushed
the
use-case-chapters
branch
from
41616bf
to
c34ca97
Compare
copySignature and pasteSignature are used to capture and re-use the C definition of various interfaces. useful for the upcoming use cases chaper which will want to include copies of the signatures without creating duplicates in the source code. also adds a few shorthand commands for headers
SteVwonder
force-pushed
the
use-case-chapters
branch
from
c34ca97
to
31d3dc2
Compare
SteVwonder
force-pushed
the
jjhursey-ex-source
branch
from
717b52c
to
ec629f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The functionality slices WG's first draft of the use cases chapter.
Includes changes to almost every
codepar, such that the contents are copied into the latex clipboard and later pasteable with thepasteSignaturemacro. A script was included inbinto automate this process.Additionally adds a new chapter (currently chapter 3) with details about Business Card Exchange, Tools & Debugging, and Hybrid Programming Models (MPI Sessions conversion to Latex still in progress).
Current version of the PDF: pmix-standard.pdf