[libfabric-users] Scalable endopint issue

Biddiscombe, John A. john.biddiscombe at cscs.ch
Thu Dec 9 13:24:06 PST 2021

I forgot to ask ...

When sending a message, the Tx context/endpoint can just send. No real problem.

When receiving, suppose I have two Rx contexts and I post a receive on both and a message arrives - if they are tagged messages, then presumably whichever Rx has the right tag will receive it - if untagged, is it just round robiin, or chance/race to see which cq is given the receive?



From: Libfabric-users <libfabric-users-bounces at lists.openfabrics.org> on behalf of Biddiscombe, John A. <john.biddiscombe at cscs.ch>
Sent: 09 December 2021 22:18:55
To: libfabric-users at lists.openfabrics.org
Subject: [libfabric-users] Scalable endopint issue

Hi list,

I am creating a scalable endpoint, which I've used previously with multiple Tx contexts, and it worked fine, but I hadn't realized you could also have multiple Rx contexts - so I added them recently ... but

I get completions on the Tx CQ, but not on the Rx CQ (GNI provider).

My initialization for both is essentially the same

Loop N thread counter

  fi_tx_context(i ... ep_tx)


  bind_queue_to_endpoint(ep_tx, cq)


  fi_rx_context(i ... ep_rx)


  bind_queue_to_endpoint(ep_rx, cq)


end loop

scalable_endpoint_bind  (address vector)

Sends are posted to the tx context/endpoint and cq

Recvs to the rx context/ep + cq

Why might there be a difference between the Tx and Rx completions? Any idea what might need tweaking



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/libfabric-users/attachments/20211209/ae186555/attachment.htm>

More information about the Libfabric-users mailing list