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

core,prov/efa: Regulate the usage of optnames #10703

Merged
merged 2 commits into from
Jan 20, 2025

Conversation

shijin-aws
Copy link
Contributor

This PR contains two commits to regulate the usage of some optnames for the fi_setopt/fi_getopt calls,
including the EFA specific ones:

FI_OPT_EFA_USE_DEVICE_RDMA, FI_OPT_EFA_SENDRECV_IN_ORDER_ALIGNED_128_BYTES,
and FI_OPT_EFA_WRITE_IN_ORDER_ALIGNED_128_BYTES

and the common one: FI_OPT_SHARED_MEMORY_PERMITTED

@shijin-aws shijin-aws requested a review from a team January 15, 2025 16:42
@shijin-aws shijin-aws requested a review from j-xiong January 15, 2025 16:45
FI_OPT_EFA_USE_DEVICE_RDMA, FI_OPT_EFA_SENDRECV_IN_ORDER_ALIGNED_128_BYTES,
and FI_OPT_EFA_WRITE_IN_ORDER_ALIGNED_128_BYTES should only apply to
the fi_setopt call as they are used to enforce the endpoint to perform
required operations. If they are not set, provider will do the traffic
with supported capabilities by default. In that regard, it causes confusions
to support these optnames in the getopt calls.

Signed-off-by: Shi Jin <[email protected]>
FI_OPT_SHARED_MEMORY_PERMITTED is used to enforce
an endpoint to NOT use shm in the data transfer.
It should only apply to the fi_setopt call, in
the same model of FI_OPT_CUDA_API_PERMITTED.

Signed-off-by: Shi Jin <[email protected]>
@shijin-aws
Copy link
Contributor Author

bot:aws:retest

@shijin-aws shijin-aws merged commit 950fb1b into ofiwg:main Jan 20, 2025
12 checks passed
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.

4 participants