From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Michael Guralnik <michaelgur@mellanox.com>,
<linux-rdma@vger.kernel.org>, Maor Gottlieb <maorg@mellanox.com>,
Mark Bloch <markb@mellanox.com>
Subject: Re: [PATCH rdma-rc] RDMA/mlx5: Fix flow destination setting for RDMA TX flow table
Date: Wed, 5 Aug 2020 21:21:30 -0300 [thread overview]
Message-ID: <20200806002130.GA958775@nvidia.com> (raw)
In-Reply-To: <20200803055849.14947-1-leon@kernel.org>
On Mon, Aug 03, 2020 at 08:58:49AM +0300, Leon Romanovsky wrote:
> From: Michael Guralnik <michaelgur@mellanox.com>
>
> For RDMA TX flow table, set destination type to be 'port' and prevent
> creation of flows with TIR destination.
>
> As RDMA TX is an egress flow table the rules on this flow table should
> not forward traffic back to the NIC and should set the destination to be
> the port.
>
> Without the setting of this destination type flow rules on the RDMA TX
> flow tables are not created as FW invokes a syndrome for undefined
> destination for the rule.
>
> Fixes: 24670b1a3166 ("net/mlx5: Add support for RDMA TX steering")
> Signed-off-by: Michael Guralnik <michaelgur@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
> drivers/infiniband/hw/mlx5/fs.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Applied to for-next for this merge window, thanks
Jason
prev parent reply other threads:[~2020-08-06 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 5:58 [PATCH rdma-rc] RDMA/mlx5: Fix flow destination setting for RDMA TX flow table Leon Romanovsky
2020-08-06 0:21 ` 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=20200806002130.GA958775@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=markb@mellanox.com \
--cc=michaelgur@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 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.