ucx
ucx copied to clipboard
UCT/API: fixup for uct_ep_connect_to_ep_v2
What
Fixed backward compatibility issue
How ?
- due to compatibility issue updated uct_ep_connect_to_ep_v2 routine parameters
- added uct_ep_connect_to_ep_param_field_t enum to add ep_address length
- iface address will not be used in ep_connect_to_ep routine
@yosefe ok to merge?
@shamisp @tonycurtis can you pls review?
Can you please provide additional details about backward compatibility issue ?
Can you please provide additional details about backward compatibility issue ?
this is issue in wire compatibility. we were going to extend rc_x iface address flags by new bits, but we found that in older versions of UCX there is exact comparing of flags with some values and adding non-zero bits to address bytes breaks compatibility
https://github.com/openucx/ucx/pull/8352 - this is regression PR
It appeared that we can't extend iface address, like it is done in #8352 without breaking wire compatibility. So the new approach is to introduce new API which also accepts address length, so that the transport can determine (in compatible way) whether the address contains an extension
/azp run
Azure Pipelines successfully started running 3 pipeline(s).