From: Christoph Lameter <cl@gentwo.de>
To: Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH][FIX] ROCE Multicast: Do not send IGMP leaves for sendonly Multicast groups
Date: Wed, 15 Sep 2021 21:44:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2109152141480.3690@gentwo.de> (raw)
In-Reply-To: <YT8qM0IpIslXL4Ni@unreal>
On Mon, 13 Sep 2021, Leon Romanovsky wrote:
> On Wed, Sep 08, 2021 at 01:43:28PM +0200, Christoph Lameter wrote:
> > ROCE uses IGMP for Multicast instead of the native Infiniband system where
> > joins are required in order to post messages on the Multicast group.
>
> According to the IBTA v1.5, there is no need to join multicast group to
> send messages.
This is ROCE where you do not need to do a join since its Ethernet
Multicast.
On Infiniband (which this patch is not dealing with) you can only send if
you join a multicast group by sending a join request with the MGID to the
SM. SM will reconfigure the IB switches so that your traffic can be routed
to the receivers of the multicast channel.
See the sendonly join description in the IBTA manuals.
> 10.5.2 MULTICAST WORK REQUESTS
> 10.5.2.1 IBA UNRELIABLE MULTICAST WORK REQUESTS
> ...
> A QP is not required to be attached to a Multicast Group
> in order to initiate an IBA Unreliable Multicast Work Request.
>
> Did I look in wrong place?
Work request? Does that mean it send multicast?
next prev parent reply other threads:[~2021-09-15 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 11:43 [PATCH][FIX] ROCE Multicast: Do not send IGMP leaves for sendonly Multicast groups Christoph Lameter
2021-09-13 10:38 ` Leon Romanovsky
2021-09-14 18:38 ` Jason Gunthorpe
2021-09-15 19:44 ` Christoph Lameter [this message]
2021-09-14 18:57 ` Jason Gunthorpe
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=alpine.DEB.2.22.394.2109152141480.3690@gentwo.de \
--to=cl@gentwo.de \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).