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.

Sign up for GitHub

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

Jump to bottom

libfabric-2.0: separate FI_DIRECTED_RECV capability for message and tagged message #9969

Open
j-xiong opened this issue Apr 2, 2024 · 3 comments
Open

libfabric-2.0: separate FI_DIRECTED_RECV capability for message and tagged message #9969

j-xiong opened this issue Apr 2, 2024 · 3 comments
Labels
API update ofi-2.0

Comments

@j-xiong
Copy link
Contributor

j-xiong commented Apr 2, 2024

Define new bits that only applies to message or tagged message. The original cap covers both.
@j-xiong
Copy link
Contributor Author

j-xiong commented Apr 2, 2024

The purpose is to allow transport to support only one of them due to hardware limitation.

@raffenet
Copy link
Contributor

raffenet commented Apr 2, 2024

MPICH only utilizes this capability for tagged messages, so splitting it should be no issue for us.

@swelch
Copy link
Contributor

swelch commented Apr 4, 2024

It also allows enables full non-matching interface performance with FI_MSG (no initiator matching) while maintaining full matching for FI_TAGGED (tag and initiator) even if hardware supports it for both. Seems particularly useful in the above use case where FI_DIRECTED_RECV is only used on FI_TAGGED.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API update ofi-2.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@raffenet @swelch @j-xiong