From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Ori Kam <orika@nvidia.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Shahaf Shuler <shahafs@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix vni matching with non-std port at ConnectX-5
Date: Tue, 3 Aug 2021 06:51:40 +0000 [thread overview]
Message-ID: <DM6PR12MB3753201142BA898E71C2328FDFF09@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210802122048.555306-1-rongweil@nvidia.com>
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Monday, August 2, 2021 15:21
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon <thomas@monjalon.net>; Shahaf Shuler
> <shahafs@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: [PATCH v2] net/mlx5: fix vni matching with non-std port at
> ConnectX-5
>
> In the recent update, the misc5 matcher was introduced to match VxLAN
> header extra fields. However, ConnectX-5 doesn't support misc5 for the UDP
> ports different from VXLAN's standard one (4789).
>
> Need to fall back to the previous approach and use legacy misc matcher if
> non-standard UDP port is recognized in VxLAN flow.
>
> Fixes: 630a587bfb37 ("net/mlx5: support matching on VXLAN reserved field")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-08-03 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 10:26 [dpdk-dev] [PATCH] net/mlx5: fix vni matching with non-std port Rongwei Liu
2021-08-02 11:09 ` Thomas Monjalon
2021-08-02 12:20 ` [dpdk-dev] [PATCH v2] net/mlx5: fix vni matching with non-std port at ConnectX-5 Rongwei Liu
2021-08-03 6:43 ` Slava Ovsiienko
2021-08-03 6:51 ` Slava Ovsiienko [this message]
2021-08-03 12:45 ` Thomas Monjalon
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=DM6PR12MB3753201142BA898E71C2328FDFF09@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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.