Skip to content

Comments

man: Clarify parameter behavior for 0 byte operations#11887

Open
a-szegel wants to merge 1 commit intoofiwg:mainfrom
a-szegel:doc-update-for-0-byte-operations
Open

man: Clarify parameter behavior for 0 byte operations#11887
a-szegel wants to merge 1 commit intoofiwg:mainfrom
a-szegel:doc-update-for-0-byte-operations

Conversation

@a-szegel
Copy link
Contributor

Note: This doc update outlines new behavior that not all providers might currently support (including efa-direct).

Clarify parameter behavior for 0 byte send/tagged/rma operations. The parameters that have been clarified are buf, iov, desc. Also clarify the parameters msg_iov, desc, and iov_count for the *msg api's.

@a-szegel a-szegel requested review from a team and j-xiong February 11, 2026 23:26
@j-xiong
Copy link
Contributor

j-xiong commented Feb 11, 2026

Maybe also clarify the count parameter since iov_count is clarified.

Clarify parameter behavior for 0 byte send/tagged/rma operations.
The parameters that have been clarified are buf, iov, desc. Also
clarify the parameters msg_iov, desc, and iov_count for the *msg
api's.

Signed-off-by: Seth Zegelstein <szegel@amazon.com>
@a-szegel a-szegel force-pushed the doc-update-for-0-byte-operations branch from fb76608 to 3ac927a Compare February 13, 2026 04:01
@a-szegel
Copy link
Contributor Author

There is a chance that not all providers currently adhere to this new requirement. How do we want to deal with that. I would also like to hold off merging until we get an AWS approver.


*iov*
: Vectored data buffer.
: Vectored data buffer. For 0-byte operations, iov may be NULL.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is a count of 1 and iov[0].buf = NULL and iov[0].len = 0 legal?

Why NULL and not just "ignored"?

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.

3 participants