From: Thomas Monjalon <thomas@monjalon.net>
To: Rongwei Liu <rongweil@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
dev@dpdk.org, "stable@dpdk.org" <stable@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] net/mlx5: fix vni matching with non-std port at ConnectX-5
Date: Tue, 03 Aug 2021 14:45:01 +0200 [thread overview]
Message-ID: <1895293.RnesTUdgTu@thomas> (raw)
In-Reply-To: <DM6PR12MB3753201142BA898E71C2328FDFF09@DM6PR12MB3753.namprd12.prod.outlook.com>
> > 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>
new title: net/mlx5: fix VXLAN VNI matching on ConnectX-5
Applied, thanks.
prev parent reply other threads:[~2021-08-03 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 10:26 [dpdk-stable] [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-stable] [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
2021-08-03 12:45 ` Thomas Monjalon [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=1895293.RnesTUdgTu@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).