From: Leon Romanovsky <leon@kernel.org>
To: Christoph Lameter <cl@gentwo.de>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Mark Zhang <markzhang@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
syzbot+8fcbb77276d43cc8b693@syzkaller.appspotmail.com
Subject: Re: [PATCH rdma-rc] RDMA/cma: Limit join multicast to UD QP type only
Date: Wed, 13 Apr 2022 11:04:25 +0300 [thread overview]
Message-ID: <YlaECWTh+NDGMxsr@unreal> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2204121653490.374115@gentwo.de>
On Tue, Apr 12, 2022 at 05:01:36PM +0200, Christoph Lameter wrote:
> On Tue, 12 Apr 2022, Jason Gunthorpe wrote:
>
> > The only places setting non-default qkeys are SIDR, maybe nobody uses
> > SIDR with multicast.
>
>
> IP port numbers provided are ignored by the RDMA subsytem when doing
> multicast joins. Thus no need to do SIDRs with RDMA multicast.
>
> Some middleware solutions (like LLM by IBM and Confinity) are creating
> their own custom MGID because of this problem. The custom MGID will then
> contain the port number.
>
> On the subject of this patch: There is a usecase for Multicast with
> IBV_QPT_RAW_PACKET too. A multicast join is required to redirect traffic
> for a multicast group to the raw socket.
The qp_type in rdma-cm is a little bit misleading and represents
communication QP. It can be or RC or UD, which is hard coded in
almost all rdma-cm code.
The one of the places that receive it from the user space is ucma_get_qp_type()
for RDMA_PS_IB flow, but librdmacm set it to RC too.
790
791 int rdma_create_id(struct rdma_event_channel *channel,
792 struct rdma_cm_id **id, void *context,
793 enum rdma_port_space ps)
794 {
795 enum ibv_qp_type qp_type;
796
797 qp_type = (ps == RDMA_PS_IPOIB || ps == RDMA_PS_UDP) ?
798 IBV_QPT_UD : IBV_QPT_RC;
799 return rdma_create_id2(channel, id, context, ps, qp_type);
800 }
801
Thanks
next prev parent reply other threads:[~2022-04-13 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 14:52 [PATCH rdma-rc] RDMA/cma: Limit join multicast to UD QP type only Leon Romanovsky
2022-04-08 18:24 ` Jason Gunthorpe
2022-04-10 12:03 ` Leon Romanovsky
2022-04-12 14:11 ` Jason Gunthorpe
2022-04-12 15:01 ` Christoph Lameter
2022-04-13 8:04 ` Leon Romanovsky [this message]
2022-04-13 8:07 ` Leon Romanovsky
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=YlaECWTh+NDGMxsr@unreal \
--to=leon@kernel.org \
--cc=cl@gentwo.de \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=syzbot+8fcbb77276d43cc8b693@syzkaller.appspotmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.