All of lore.kernel.org
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>, Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH] net/mlx5: fix integrity conversion scheme
Date: Thu, 11 Nov 2021 16:51:27 +0000	[thread overview]
Message-ID: <DM6PR12MB37532E958D13CF365BC0D944DF949@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211111161627.10436-1-getelson@nvidia.com>

> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Thursday, November 11, 2021 18:16
> To: dev@dpdk.org; Gregory Etelson <getelson@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>
> Cc: stable@dpdk.org; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: fix integrity conversion scheme
> 
> RTE flow integrity API provides top-level packet validations.
> RTE integrity bits are not always translated one-to-one to hardware integrity
> bits.
> For example RTE l3_ok and l4_ok integrity bits require 2 hardware integrity
> bits each.
> 
> The patch fixes RTE l3_ok and l4_ok bits translation to match
> ConnectX-6 hardware.
> 
> Cc: stable@dpdk.org
> 
> Fixes: 79f8952783d0 ("net/mlx5: support integrity flow item")
> 
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>


  reply	other threads:[~2021-11-11 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 16:16 [PATCH] net/mlx5: fix integrity conversion scheme Gregory Etelson
2021-11-11 16:51 ` Slava Ovsiienko [this message]
2021-11-14 11:19 ` Raslan Darawsheh

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=DM6PR12MB37532E958D13CF365BC0D944DF949@DM6PR12MB3753.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=matan@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 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.