[libfabric-users] multi-receive CQ entry with FI_MULTI_RECV, not the last one read by fi_cq_read()?

[Titus, Greg]

Hi Sean --

I called fi_cq_read(cq, buf, 5) and it filled in buf with 5 entries.  buf[0].flags==FI_MSG|FI_RECV and buf[0].buf was near the end of the multi-receive buffer.  buf[1].flags==FI_MULTI_RECV.  buf[2].flags==FI_MSG|FI_RECV and buf[2].buf was much earlier in the multi-receive buffer than buf[0].buf.  buf[3] and buf[4] were the same as buf[2] but with different .buf pointers though both were also much earlier in the multi-receive buffer than buf[0].buf.

greg


________________________________
From: Hefty, Sean <sean.hefty at intel.com>
Sent: Wednesday, June 24, 2020 4:17 PM
To: Titus, Greg <gregory.titus at hpe.com>; libfabric-users at lists.openfabrics.org <libfabric-users at lists.openfabrics.org>
Subject: RE: multi-receive CQ entry with FI_MULTI_RECV, not the last one read by fi_cq_read()?

> Hmm, interesting.  My only ordering assertions are that I have
> FI_ORDER_RMA_RAW|FI_ORDER_SAS|FI_ORDER_SAW in both the tx_attr and rx_attr msg_order
> members of the hints for my fi_getinfo(). In the tx_attr and rx_attr op_flags I've just
> got FI_COMPLETION. But the CQ entry with the FI_MULTI_RECV flag set was entry 1 out of
> a range of 0..4, as I said. Definitely not the last one.

At least with rxm, the completion that reports that a multi-recv buffer has been consumed is not associated with a message.  I'm not sure what you mean by entry 1 out of a range of 0 to 4.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/libfabric-users/attachments/20200624/4b02ebbb/attachment-0001.htm>