All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: <mwilck@suse.com>
Cc: <linux-rdma@vger.kernel.org>, Zhu Yanjun <zyjzyj2000@gmail.com>,
	"Mohammad Heib" <goody698@gmail.com>,
	Nicolas Morey-Chaisemartin <nmoreychaisemartin@suse.com>
Subject: Re: [PATCH v2] Revert "RDMA/rxe: Remove VLAN code leftovers from RXE"
Date: Wed, 20 Jan 2021 13:24:41 -0400	[thread overview]
Message-ID: <20210120172441.GA1099203@nvidia.com> (raw)
In-Reply-To: <20210120161913.7347-1-mwilck@suse.com>

On Wed, Jan 20, 2021 at 05:19:13PM +0100, mwilck@suse.com wrote:
> From: Martin Wilck <mwilck@suse.com>
> 
> This reverts commit b2d2440430c0fdd5e0cad3efd6d1c9e3d3d02e5b.
> 
> It's true that creating rxe on top of 802.1q interfaces doesn't work.
> Thus, commit fd49ddaf7e26 ("RDMA/rxe: prevent rxe creation on top of vlan interface")
> was absolutely correct.
> 
> But b2d2440430c0 was incorrect assuming that with this change,
> RDMA and VLAN don't work togehter at all. It just has to be
> set up differently. Rather than creating rxe on top of the VLAN
> interface, rxe must be created on top of the physical interface.
> RDMA then works just fine through VLAN interfaces on top of that
> physical interface, via the "upper device" logic.
> 
> I've tested this mainly with NVMe over RDMA and rping, but I don't
> see why it wouldn't work just as well for other protocols. If there
> are real issues, I'd like to know.
> 
> b2d2440430c0 broke this setup deliberately and should thus be
> reverted. Also, b2d2440430c0 removed rxe_dma_device() (which is
> indeed not necessary), but not its declaration in rxe_loc.h.
> 
> Fixes: b2d2440430c0 ("RDMA/rxe: Remove VLAN code leftovers from RXE")
> 
> Cc: Zhu Yanjun <zyjzyj2000@gmail.com>
> Cc: Mohammad Heib <goody698@gmail.com>
> Cc: Nicolas Morey-Chaisemartin <nmoreychaisemartin@suse.com>
> Signed-off-by: Martin Wilck <mwilck@suse.com>
> ---
>  drivers/infiniband/sw/rxe/rxe_loc.h  | 1 -
>  drivers/infiniband/sw/rxe/rxe_net.c  | 6 ++++++
>  drivers/infiniband/sw/rxe/rxe_resp.c | 5 +++++
>  3 files changed, 11 insertions(+), 1 deletion(-)

Applied to for-rc, thanks

Jason

  reply	other threads:[~2021-01-20 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 16:19 [PATCH v2] Revert "RDMA/rxe: Remove VLAN code leftovers from RXE" mwilck
2021-01-20 17:24 ` Jason Gunthorpe [this message]
2021-01-20 17:31 ` 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=20210120172441.GA1099203@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=goody698@gmail.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mwilck@suse.com \
    --cc=nmoreychaisemartin@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.