> It seems to me that using a Shared Rx context and 1 CQ with connected > endpoints is very > much like running connectionless: when a message is received, I cannot see an > obvious > way to determine the source of the message. The CQ entry does not have the > endpoint in > it and I cannot get AVs to work with the TCP or verbs provider (thus I cannot > use > fi_cq_readfrom).
I agree - this is an issue. > Is there an easy way to determine the source address/endpoint of a received > message in > this scenario? Would it make sense to include the ep fid in the CQ entry to > help? Some sort of extension is needed here. I'm not sure what the best answer is. IMO, the ideal solution would make use of fi_cq_readfrom(), so that the source data is reported the same way regardless of EP type. I just don't see a clean way to do this off the top of my head. - Sean _______________________________________________ ofiwg mailing list [email protected] https://lists.openfabrics.org/mailman/listinfo/ofiwg
