From: Jason Gunthorpe <jgg@nvidia.com>
To: Martin Wilck <mwilck@suse.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Leon Romanovsky <leon@kernel.org>,
Mohammad Heib <goody698@gmail.com>
Subject: Re: Revert "RDMA/rxe: Remove VLAN code leftovers from RXE"
Date: Wed, 20 Jan 2021 11:45:31 -0400 [thread overview]
Message-ID: <20210120154531.GU4147@nvidia.com> (raw)
In-Reply-To: <9ae3161750dfc8500b68b68c94a092d10ae785f4.camel@suse.com>
On Wed, Jan 20, 2021 at 04:28:43PM +0100, Martin Wilck wrote:
> > If your use case that work was creating a rxe on a upper vlan device
> > and relying on the tx of vlan layer to stuff the vlan, then the
> > problem is how the core code manages the gid table.
>
> My use case was creating RXE on the physical device, creating VLANs on
> top of the same physical device, and create RDMA connections over these
> VLANs. This is what used to work.
Hurm.
So, since rxe never touches the vlan on the tx path, I always thought
it was busted here.
But, it extracts the netdev from the gid_attr and uses that netdev to
tx the skb, which does stuff the correct vlan.
And the rx path, though it is hard to find, does check the gid table
with the vlan, again indirectly through the netdev
So the removed hunk in do_complete is OK
The hunk in rxe_udp_encap_recv is finding the ib_device to use from an
uppser, also OK
The stuff with rxe_dma_device is wrong, just delete that hunk
completely.
So sure, lets apply this - with the rxe_dma_device() part removed
though.
Jason
next prev parent reply other threads:[~2021-01-20 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 5:33 Revert "RDMA/rxe: Remove VLAN code leftovers from RXE" Zhu Yanjun
2021-01-20 14:30 ` Martin Wilck
2021-01-20 14:44 ` Zhu Yanjun
2021-01-20 15:04 ` Martin Wilck
2021-01-20 15:19 ` Jason Gunthorpe
2021-01-20 15:28 ` Martin Wilck
2021-01-20 15:45 ` Jason Gunthorpe [this message]
2021-01-20 16:18 ` Martin Wilck
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=20210120154531.GU4147@nvidia.com \
--to=jgg@nvidia.com \
--cc=goody698@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mwilck@suse.com \
--cc=zyjzyj2000@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.