From: Jason Gunthorpe <jgg@nvidia.com>
To: Mohammad Heib <goody698@gmail.com>
Cc: <linux-rdma@vger.kernel.org>, <yanjunz@mellanox.com>,
<dledford@redhat.com>, <kamalheib1@gmail.com>, <leon@kernel.org>
Subject: Re: [PATCH] RDMA/rxe: prevent rxe creation on top of vlan interface
Date: Mon, 24 Aug 2020 14:14:42 -0300 [thread overview]
Message-ID: <20200824171442.GA3213679@nvidia.com> (raw)
In-Reply-To: <20200811150415.3693-1-goody698@gmail.com>
On Tue, Aug 11, 2020 at 06:04:15PM +0300, Mohammad Heib wrote:
> Creating rxe device on top of vlan interface will create a non-functional device
> that has an empty gids table and can't be used for rdma cm communication.
>
> This is caused by the logic in enum_all_gids_of_dev_cb()/is_eth_port_of_netdev(),
> which only considers networks connected to "upper devices" of the configured
> network device, resulting in an empty set of gids for a vlan interface,
> and attempts to connect via this rdma device fail in cm_init_av_for_response
> because no gids can be resolved.
>
> apparently, this behavior was implemented to fit the HW-RoCE devices that create
> RoCE device per port, therefore RXE must behave the same like HW-RoCE devices
> and create rxe device per real device only.
>
> In order to communicate via a vlan interface, the user must use the gid index of
> the vlan address instead of creating rxe over vlan.
>
> Signed-off-by: Mohammad Heib <goody698@gmail.com>
> ---
> drivers/infiniband/sw/rxe/rxe.c | 6 ++++++
> drivers/infiniband/sw/rxe/rxe_sysfs.c | 6 ++++++
> 2 files changed, 12 insertions(+)
It would be better to somehow fix things so the gid table was properly
populated, but until that is done, blocking it is a reasonable thing
to do.
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-08-24 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 15:04 [PATCH] RDMA/rxe: prevent rxe creation on top of vlan interface Mohammad Heib
2020-08-13 3:16 ` Zhu Yanjun
2020-08-13 9:52 ` mohammad
2020-08-13 16:13 ` Zhu Yanjun
2020-08-24 17:14 ` 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=20200824171442.GA3213679@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=goody698@gmail.com \
--cc=kamalheib1@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjunz@mellanox.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;
as well as URLs for NNTP newsgroup(s).