From: Leon Romanovsky <leon@kernel.org>
To: Christoph Lameter <cl@gentwo.org>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org
Subject: Re: rdma-core: Add support for multicast loopback prevention to mckey
Date: Sun, 5 Dec 2021 15:26:16 +0200 [thread overview]
Message-ID: <Yay9+MyBBpE4A7he@unreal> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2112021404100.58561@gentwo.de>
On Thu, Dec 02, 2021 at 02:36:48PM +0100, Christoph Lameter wrote:
> The rdma_create_qp createflags option IBV_QP_CREATE_BLOCK_SELF_MCAST_LB
> should prevent multicast loopback. However, this feature seems to be
> broken on a lot of RDMA NICs and there is no way to test this with the
> existing RDMA tools. So add an option to mckey in order to allow to send
> multicast messages without loopback. mckey's default has been and will
> continue to be to loopback all multicast messages.
>
> Loopback of multicast messages can have surprising effects because all
> messages sent out also have to be processed locally by all members of
> the multicast group. This usually also includes the sender.
>
> In order to test multicast loop execute the following in two windows
> on a host connected to an RDMA fabric.
>
> First session (Receiver)
>
> mckey -b <RDMA IP address> -m239.1.2.1
>
> Second session (Sender)
>
> mckey -b <RDMA IP address> -m239.1.2.2 -s -l
>
>
> The sender will send 10 messages and the receiver will terminate
> after 10 messages have been received.
>
> If loopback prevention would work then the receiver should only
> terminate on its own when the -l option has not been specified.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Christoph,
How can I apply your patch? Can you send it as a PR to rdma-core github?
Thanks
next prev parent reply other threads:[~2021-12-05 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 13:36 rdma-core: Add support for multicast loopback prevention to mckey Christoph Lameter
2021-12-05 13:26 ` Leon Romanovsky [this message]
2021-12-06 7:13 ` Christoph Lameter
2021-12-06 7:28 ` Leon Romanovsky
2021-12-06 12:18 ` Christoph Lameter
2021-12-06 15:33 ` Jason Gunthorpe
2021-12-06 18:39 ` Christoph Lameter
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=Yay9+MyBBpE4A7he@unreal \
--to=leon@kernel.org \
--cc=cl@gentwo.org \
--cc=jgg@nvidia.com \
--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