Skip to content

prov/shm: inject protocol changes DO NOT MERGE for testing purposes only#12174

Closed
aingerson wants to merge 2 commits intoofiwg:mainfrom
aingerson:zach
Closed

prov/shm: inject protocol changes DO NOT MERGE for testing purposes only#12174
aingerson wants to merge 2 commits intoofiwg:mainfrom
aingerson:zach

Conversation

@aingerson
Copy link
Copy Markdown
Contributor

No description provided.

zachdworkin and others added 2 commits April 9, 2026 09:39
Remove the parallel command-inject resources and revert
to using a lock-unlock inject buffer pool.

Update the inject protocol to use the old method.

There is a performance regression when using the "new shm"
command-inject parallel data structure. This is due to the
sender not being able to complete its transmission until
the receiver returns the sender's command to the sender's
return queue. In the old lock-unlock method the sender
would allocate receiver side resources, copy its data into
the receiver inject buffer and then complete. The old
method allows MPIs and applications to assume that their
inject message transmissions will complete quickly and
since the new method does not complete `as` quickly it is
likely the reason for this regression.

Signed-off-by: Zach Dworkin <zachary.dworkin@intel.com>
Signed-off-by: Alexia Ingerson <alexia.ingerson@intel.com>
@zachdworkin
Copy link
Copy Markdown
Contributor

I slurped up the patch in my PR #12109

@zachdworkin zachdworkin closed this May 1, 2026
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

Successfully merging this pull request may close these issues.

2 participants