For the RC transport, the answer is yes. You definitely need one queue pair per client at the server, although it could be possible for the QPs at the server to share an event channel. But UD transport is also pretty "reliable" as packet loss in any InfiniBand transport is extremely rare. A rather high ballpark is one in a billion. --Anuj On Mon, Nov 3, 2014 at 5:59 PM, Just Floaterions <floaterions@xxxxxxxxx> wrote: > Thank you for your help. So the question is, for reliable connections, do I > need separate event channel/queue-pairs for each connection? > > On Mon, Nov 3, 2014 at 3:50 PM, Anuj Kalia <anujkaliaiitd@xxxxxxxxx> wrote: >> >> You can do SEND/RECV over Unreliable Datagram multicast which could be >> beneficial in your situation (i.e., better than 1-1 connections). You >> can't use multicast for READs or WRITEs. >> >> --Anuj >> >> On Sun, Nov 2, 2014 at 9:32 PM, floaterions <floaterions@xxxxxxxxx> wrote: >> > Hello everyone, >> > >> > As a newbie to the world of InfiniBand programming, >> > I would appreciate your helps on my somewhat general and basic question. >> > >> > Assume that I have a server, and N clients (N > 1). >> > I would like my server to set all clients' memory buffers to some value >> > V. >> > How would I go about this problem? >> > So far, I've managed to establish 1-1 connections using >> > READ/WRITE/SEND/RECEIVE. >> > So I guess the core of my question is: >> > how 1-to-N connections are established in InfiniBand, and >> > if, in this regard, there is any difference between >> > RDMA verbs (READ/WRITE) vs. SEND/RECEIVE? >> > >> > -- >> > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in >> > the body of a message to majordomo@xxxxxxxxxxxxxxx >> > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html