From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/mlx5: fix integrity matching for inner and outer headers
Date: Thu, 28 Oct 2021 15:03:47 +0000 [thread overview]
Message-ID: <DM4PR12MB5312033F9C388775C03AADE1CF869@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211026092543.13224-1-getelson@nvidia.com>
Hi,
> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Tuesday, October 26, 2021 12:26 PM
> To: dev@dpdk.org; Gregory Etelson <getelson@nvidia.com>
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH 1/2] net/mlx5: fix integrity matching for inner and outer
> headers
>
> MLX5 PMD can match on integrity bits for inner and outer headers in
> a single flow.
> That means a single flow rule can reference both inner and outer
> integrity bits. That is implemented by adding 2 flow integrity items
> to a rule - one item for outer integrity bits and other for
> inner integrity bits.
> Integrity item `level` parameter specifies what part is being
> targeted.
>
> Current PMD treated integrity items for outer and inner headers as
> the same.
> The patch separates PMD verifications for inner and outer integrity
> items.
>
> Fixes: 79f8952783d0 ("net/mlx5: support integrity flow item")
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-10-28 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 9:25 Gregory Etelson
2021-10-26 9:25 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix integrity flow item validation and translation Gregory Etelson
2021-10-28 15:03 ` Raslan Darawsheh [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=DM4PR12MB5312033F9C388775C03AADE1CF869@DM4PR12MB5312.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--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).