Skip to content

Conversation

@ryanhankins
Copy link
Contributor

Implement fi_writedata infrastructure and support in the CXI provider, updating
MR and RMA code paths and adjusting event/key handling for writedata dual-entry mode. Gate
RMA writedata on domain->rma_cq_data_size and bump the CXI provider minor version to indicate
the new API support. Add a fi_writedata test and update the fi_cxi.7 manpage.

@ryanhankins ryanhankins changed the title Fi writemsg cxi: implement fi_writedata support, bump provider version, add tests/docs Dec 2, 2025
@swelch swelch changed the title cxi: implement fi_writedata support, bump provider version, add tests/docs prov/cxi: implement fi_writedata support Dec 2, 2025
@swelch
Copy link
Contributor

swelch commented Dec 2, 2025

@ryanhankins - Nit, individual commit heading should be "prov/cxi" or "man/fi_cxi" for these commits. The last commit in particular should also clarify "prov/cxi" as cxi unit tests are specifically being added along with your man page update.

Copy link
Contributor

@swelch swelch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a few comments for possible changes. Also, in the unit tests commit could you also update prov/cxi/test/test.sh to include a new long test suite option that sets "FI_CXI_ENABLE_WRITEDATA=1" and filters on "rma*/*". This will verify both existing RMA tests are not impacted when writedata is enabled and that the new writedata works as advertised. Thanks for getting this together.

@ryanhankins ryanhankins force-pushed the fi_writemsg branch 2 times, most recently from 81123bd to c329019 Compare December 2, 2025 20:15
Copy link
Contributor

@swelch swelch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Ryan for the changes. One more comment on documentation and two changes to consider on forcing FI_MR_PROV_KEY usage. Changes look good.

@ryanhankins ryanhankins force-pushed the fi_writemsg branch 3 times, most recently from 128e65f to 1089aec Compare December 4, 2025 18:00
swelch
swelch previously approved these changes Dec 4, 2025
Copy link
Contributor

@swelch swelch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

@swelch swelch requested a review from jswaro December 5, 2025 16:57
@swelch
Copy link
Contributor

swelch commented Dec 5, 2025

@shijin-aws - any worries on the AWS CI failure, changes are self-contained to cxi?

@swelch
Copy link
Contributor

swelch commented Dec 8, 2025

bot:aws:retest

3 similar comments
@Zhenye-Na
Copy link
Contributor

bot:aws:retest

@Zhenye-Na
Copy link
Contributor

bot:aws:retest

@sielicki
Copy link
Contributor

bot:aws:retest

Copy link
Contributor

@swelch swelch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See latest comments regarding a few changes.

@ryanhankins ryanhankins force-pushed the fi_writemsg branch 2 times, most recently from f8d15ed to 1c01479 Compare December 16, 2025 21:11
@ryanhankins
Copy link
Contributor Author

Thank you for looking at this. I believe I've resolved the comments.

Bumped the CXI provider minor version to indicate added support for the fi_writedata API.
Integrated writedata handling by gating RMA writedata support on domain->rma_cq_data_size
and updated MR and RMA code paths to use this indicator; adjusted event and key handling
for writedata dual-entry mode.

Signed-off-by: Ryan Hankins <[email protected]>
Add fi_writedata test and update fi_cxi.7.md

Signed-off-by: Ryan Hankins <[email protected]>
@sielicki
Copy link
Contributor

sielicki commented Jan 3, 2026

sielicki@e6f28a9 would supplant this

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