From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Ori Kam <orika@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Michael Baum <michaelba@nvidia.com>,
Alex Vesker <valex@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Erez Shitrit <erezsh@nvidia.com>
Subject: RE: [PATCH] net/mlx5/hws: remove csum check from L3 ok check
Date: Tue, 31 Oct 2023 08:04:08 +0000 [thread overview]
Message-ID: <MN0PR12MB6056A7CD016A231FFDE95E2ACFA0A@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231025203918.1603751-1-akozyrev@nvidia.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Wednesday, October 25, 2023 11:39 PM
> To: dev@dpdk.org
> Cc: Ori Kam <orika@nvidia.com>; Matan Azrad <matan@nvidia.com>; Michael
> Baum <michaelba@nvidia.com>; Alex Vesker <valex@nvidia.com>; Suanming
> Mou <suanmingm@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>;
> Erez Shitrit <erezsh@nvidia.com>
> Subject: [PATCH] net/mlx5/hws: remove csum check from L3 ok check
>
> From: Michael Baum <michaelba@nvidia.com>
>
> This patch changes the integrity item behavior for HW steering.
>
> Old behavior: the "ipv4_csum_ok" checks only IPv4 checksum and "l3_ok"
> checks everything is ok including IPv4 checksum.
>
> New behavior: the "l3_ok" checks everything is ok excluding IPv4 checksum.
>
> This change enables matching "l3_ok" in IPv6 packets since for IPv6 packets
> "ipv4_csum_ok" is always miss.
> For SW steering the old behavior is kept as same as for L4 ok.
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-10-31 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 20:39 Alexander Kozyrev
2023-10-29 13:21 ` Ori Kam
2023-10-31 8:04 ` 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=MN0PR12MB6056A7CD016A231FFDE95E2ACFA0A@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=erezsh@nvidia.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=valex@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).