patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Cc: stable@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: Re: [PATCH 22.11 3/3] net/mlx5: fix flex item header length field translation
Date: Thu, 31 Oct 2024 14:34:55 +0000	[thread overview]
Message-ID: <CAMw=ZnTm3tr510e-JkdRAqnoWJxtfbH6hm8kE7Q2GJK8k0L8YQ@mail.gmail.com> (raw)
In-Reply-To: <20241031124434.1751097-3-viacheslavo@nvidia.com>

On Thu, 31 Oct 2024 at 12:45, Viacheslav Ovsiienko
<viacheslavo@nvidia.com> wrote:
>
> [ upstream commit net/mlx5: fix flex item header length field translation ]
>
> There are hardware imposed limitations on the header length
> field description for the mask and shift combinations in the
> FIELD_MODE_OFFSET mode.
>
> The patch updates:
>   - parameter check for FIELD_MODE_OFFSET for the header length
>     field
>   - check whether length field crosses dword boundaries in header
>   - correct mask extension to the hardware required width 6-bits
>   - correct adjusting the mask left margin offset, preventing
>     dword offset
>
> Fixes: b293e8e49d78 ("net/mlx5: translate flex item configuration")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_flow_flex.c | 112 +++++++++++++++++++-----------
>  1 file changed, 72 insertions(+), 40 deletions(-)

Thanks, all applied

      reply	other threads:[~2024-10-31 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 12:44 [PATCH 22.11 1/3] net/mlx5: update flex parser arc types support Viacheslav Ovsiienko
2024-10-31 12:44 ` [PATCH 22.11 2/3] net/mlx5: fix non full word sample fields in flex item Viacheslav Ovsiienko
2024-10-31 12:44 ` [PATCH 22.11 3/3] net/mlx5: fix flex item header length field translation Viacheslav Ovsiienko
2024-10-31 14:34   ` Luca Boccassi [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='CAMw=ZnTm3tr510e-JkdRAqnoWJxtfbH6hm8kE7Q2GJK8k0L8YQ@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=dsosnowski@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).