-
Notifications
You must be signed in to change notification settings - Fork 489
DEVICE: Document return status for device APIs #10940
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
base: master
Are you sure you want to change the base?
DEVICE: Document return status for device APIs #10940
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIR we told that UCS_INPROGRESS should be returned only on UCT layer. Is it useful to return UCS_INPROGRESS to UCP API user?
@Artemy-Mellanox currently UCP returns |
|
It would require testing and updating the tests, let's discuss tomorrow and for now update documentation according to the current implementation. |
What?
Following #10928
Update UCT and UCP device API documentation to specify that send operations return
UCS_INPROGRESS
when successfully posted andUCS_OK
when successfully completed.Why?
Following #10928 the device send functions return
UCS_INPROGRESS
after posting operations (for gda_rc, not_cuda_ipc), but the documentation only stated generic "Error code as defined by ucs_status_t" without clarifying the expected return values or that completion checking is required.How?
Added explicit
UCS_INPROGRESS
andUCS_OK
documentation to all device send functions (put_single, atomic_add, put_multi, put_multi_partial) at both UCT and UCP layers.