public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: udaddy.c question
Date: Fri, 12 Mar 2010 09:25:14 -0600	[thread overview]
Message-ID: <4B9A5CDA.1030704@opengridcomputing.com> (raw)

Hello rdma wizards,

I'm trying to understand how IB UD service works with the rdmacm in 
linux.  According to the IBTA specification, I should be able to create 
a single UD QP and exchange messages with any number of peers as long as 
I know their qkeys.  Yet when I look at udaddy.c (and even mckey.c), it 
appears that the UD service in the rdmacm is really connection oriented 
and a QP is required for each pair of processes exchanging data.  I 
think this is just the way udaddy.c was implemented, but I want to know 
if it is possible with librdmacm to create a single cm_id with a single 
QP, bind it to an IP address/port, and then send/recv to multiple peers 
(via unicast).  Is this possible?

Thanks!

Steve.


--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2010-03-12 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 15:25 Steve Wise [this message]
     [not found] ` <4B9A5CDA.1030704-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-03-12 16:37   ` udaddy.c question Sean Hefty
     [not found]     ` <87571B1E12964DEE8582290B804E03A8-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-03-12 17:06       ` Steve Wise
     [not found]         ` <4B9A74A4.8030404-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2010-03-12 17:36           ` Sean Hefty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B9A5CDA.1030704@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox