-
Notifications
You must be signed in to change notification settings - Fork 389
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
Allow re-use of fi_info returned from fi_getinfo #49
Comments
A possible solution is for the FI_CONNREQ event to return a connection 'context' to the application. The context is in the fi_eq_cm_entry structure. (part of fi_eq_entry header). This context can be provided as input into cm::accept or reject. The drawback is that the EP will be created and enabled without knowing that it will be associated with the connection. This seems doable, though it may require software to track the EP creation and configuration until accept is called. This approach could eliminate the data field from fi_info. |
This change should remove the provider specific freeinfo call. |
Addressed in commit 6b0bbb7 |
add EQ unit test "unit/fi_eq_test"
contrib/cray: Add XRC testing with SFT
…g#49) LEX-4099 - Fix bad error check in fi_mr_reg * LEX-4099 - Fix bad error check in fi_mr_reg Fix bad error check in fi_mr_reg, and add more logging Signed-off-by: Benjamin Kitor <bkitor@gigaio.com> Approved-by: Tadeusz Struk Approved-by: Eric Pilmore
The struct fi_info returned from fi_getinto may only be used once. Redefine the API to allow the fi_info to be used multiple times. This will require changes from the verbs provider to handle the 'data' field differently. Note that the data field is also used when establishing a connection request.
The text was updated successfully, but these errors were encountered: