From: Kevin Traynor <ktraynor@redhat.com>
To: Matan Azrad <matan@nvidia.com>,
stable@dpdk.org, Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix tunnel flow prioriity
Date: Thu, 17 Dec 2020 11:41:25 +0000 [thread overview]
Message-ID: <490677a6-78e8-fa60-f588-06fca63fbd78@redhat.com> (raw)
In-Reply-To: <1607884412-242890-1-git-send-email-matan@nvidia.com>
On 13/12/2020 18:33, Matan Azrad wrote:
> [ upstream commit 050bfe033c2dcaff1f6cfb3110aa90bf80071513 ]
>
> The PMD manages internally the priority of the flows in addition to
> the user configured priority.
> So, 2 flows with the same user priority may get different priority.
> The method:
> As much as the flow is more specific it gets higher priority
> (higher means first to be matched).
>
> In addition, When the user creates a RSS flow the PMD splits the flows
> according to the flow RSS layers as the HW requests for RSS TIR.
> The internal priority for each flow is decided by the flow last layer.
> L2, L3 and L4 (L2 low and L4 high).
>
> The tunnel layer was wrongly decided to be L4 all the time, even when
> the flow is configured with inner-RSS.
>
> Hence, the first RSS split which takes the tunnel layer priority all the
> time will be matched before the more specific splits.
>
> Change the priority of tunnel layer to be L2 when inner-RSS is
> configured.
>
> Fixes: d4a405186b73 ("net/mlx5: support tunnel RSS level")
>
> Signed-off-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_flow_dv.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Applied, thanks.
prev parent reply other threads:[~2020-12-17 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 18:33 Matan Azrad
2020-12-17 11:41 ` Kevin Traynor [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=490677a6-78e8-fa60-f588-06fca63fbd78@redhat.com \
--to=ktraynor@redhat.com \
--cc=matan@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).