From: Luca Boccassi <bluca@debian.org>
To: Gregory Etelson <getelson@nvidia.com>, stable@dpdk.org
Cc: rasland@nvidia.com, Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH 19.11] net/mlx5: fix tunnel flow priority
Date: Tue, 11 Aug 2020 18:57:21 +0100 [thread overview]
Message-ID: <62af16f9eae2f45216fbf57e455c93a7dfca5dc5.camel@debian.org> (raw)
In-Reply-To: <20200811122003.9491-1-getelson@nvidia.com>
On Tue, 2020-08-11 at 15:20 +0300, Gregory Etelson wrote:
> [ upstream commit 750ff30a8fde522477babb0d4fcdc6fb9eb21fde ]
>
> PMD flow priority is different from application flow priority. Flow
> rules with higher match granularity assigned higher PMD priority. Also
> PMD splits internally RSS flows according to flow RSS layer.
>
> Final PMD flow rule priority derived from the last match item network
> level, after PMD adjusts flow rule, where L4 match gets the highest
> priority and L2 the lowest.
>
> The patch adjusts tunnels flow rule priority calculation for PMDs
> running verb API.
>
> Fixes: 4a78c88e3bae ("net/mlx5: fix Verbs flow tunnel")
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_flow_verbs.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
Thank you, applied and pushed.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-08-11 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 12:20 Gregory Etelson
2020-08-11 17:57 ` Luca Boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-11 11:48 Gregory Etelson
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=62af16f9eae2f45216fbf57e455c93a7dfca5dc5.camel@debian.org \
--to=bluca@debian.org \
--cc=getelson@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
/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).