Peer provider addressing issues
shefty opened this issue · comments
This is related to PR #7635. The peer provider APIs need to exchange fi_addr_t data between the peer and owner provider. We want a mechanism defined that minimizes address lookups. Additionally, in a generic use case, there may be multiple AVs active in the peer. The fi_addr_t value is not sufficient to determine which peer AV the address belongs to, making a reverse lookup basically impossible by the owner.
See #7670 for a proposed solution that allows associating a user-specified id with each address.
Thank you! The solution looks reasonable to me.
Proposed changes merged upstream.