All of lore.kernel.org
 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: pyverbs testing on rxe
Date: Fri, 4 Sep 2020 15:20:00 -0300	[thread overview]
Message-ID: <20200904182000.GA9166@nvidia.com> (raw)
In-Reply-To: <96da1311-18a6-f6a6-be18-9ca034ae1d7b@gmail.com>

On Fri, Sep 04, 2020 at 01:03:40PM -0500, Bob Pearson wrote:
> The unicast IPv4 address is 192.168.0.21 which does have a gid table
> entry. The multicast address is 230.168.0.21 which does
> not. Presumably the driver wants the gid table entry so it can use
> it to provide a source address for return traffic but that would
> just be the unicast address I think.

What is the call stack like around this?

It should be using a route lookup to get the src IP to map to a gid
address

> BTW I got around the other addressing problem I was having by just
> adding the eui48 IPV5 address by hand with ip addr add.

Hum, seems like this is still a core code bug that should be fixed
though

Jason

      reply	other threads:[~2020-09-04 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 18:03 pyverbs testing on rxe Bob Pearson
2020-09-04 18:20 ` Jason Gunthorpe [this message]

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=20200904182000.GA9166@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 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.