Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: rxe mcast
Date: Wed, 1 Nov 2023 15:29:49 -0300	[thread overview]
Message-ID: <20231101182949.GC1850209@nvidia.com> (raw)
In-Reply-To: <5b5d7549-1d1b-46ec-a6a3-baeaf4dfb179@gmail.com>

On Wed, Nov 01, 2023 at 01:07:28PM -0500, Bob Pearson wrote:
> Jason,
> 
> I wrote a test program to verify that multicast is working in rxe
> since there don't seem to be any pyverbs tests that actually test this.
> It turns out that it doesn't work for several reasons most of which
> I have fixed. But there is one that I can't figure out.
> 
> The rxe driver calls dev_mc_add() with a MAC address to add the
> multicast MAC address to the device which shows up when you type
> 'ip maddr'. But nothing comes through from the network to the driver.
> Wireshark does see the packets but they don't get to the IP or
> UDP layers in the netdev stack.

I think you also need to attach a multicast IP address to the RXE
socket ?

> So creating the IP mcast address seems critical to letting the
> netdev stack receive traffic.

Yes
 
> I tried creating a separate UDP socket bound to the mcast address
> but it doesn't seem to create the required IP address.

I don't think that is how you do it... There is a set sock opt thing
you need, IIRC. It has been a long time since I last wrote code for it

Check what iperf did and that will be the basic thing that has to be
cloned in the kernel

Jason

  reply	other threads:[~2023-11-01 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 18:07 rxe mcast Bob Pearson
2023-11-01 18:29 ` Jason Gunthorpe [this message]
2023-11-01 21:02   ` Bob Pearson

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=20231101182949.GC1850209@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox