From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Cc: guohongzhi1@huawei.com, keith.wiles@intel.com,
mb@smartsharesystems.com, thomas@monjalon.net,
ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru
Subject: [dpdk-dev] [PATCH v2 0/4] net/tap: fix Rx cksum
Date: Wed, 30 Jun 2021 15:51:54 +0200 [thread overview]
Message-ID: <20210630135158.8108-1-olivier.matz@6wind.com> (raw)
In-Reply-To: <20210427135755.927-1-olivier.matz@6wind.com>
This patchset fixes the Rx checksum flags in net/tap
driver. The first two patches are the effective fixes.
The last 2 patches introduce a new checksum API to
verify a L4 checksum and its unt test, in order to
simplify the net/tap code, or any other code that has
the same needs.
v2:
* clarify why RTE_PTYPE_L3_IPV4_EXT_UNKNOWN cannot happen in
tap_verify_csum() (patch 1)
* align style of rte_ipv6_udptcp_cksum_verify() to
rte_ipv4_udptcp_cksum_verify() (patch 3)
* clarify comment above rte_ipv4_udptcp_cksum_verify() and
rte_ipv6_udptcp_cksum_verify() (patch 3)
Olivier Matz (4):
net/tap: fix Rx cksum flags on IP options packets
net/tap: fix Rx cksum flags on TCP packets
net: introduce functions to verify L4 checksums
test/cksum: new test for L3/L4 checksum API
MAINTAINERS | 1 +
app/test/autotest_data.py | 6 +
app/test/meson.build | 2 +
app/test/test_cksum.c | 271 ++++++++++++++++++++++++++++++++++
drivers/net/tap/rte_eth_tap.c | 23 ++-
lib/net/rte_ip.h | 127 +++++++++++++---
6 files changed, 398 insertions(+), 32 deletions(-)
create mode 100644 app/test/test_cksum.c
--
2.29.2
next prev parent reply other threads:[~2021-06-30 13:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 13:57 [dpdk-dev] [PATCH " Olivier Matz
2021-04-27 13:57 ` [dpdk-dev] [PATCH 1/4] net/tap: fix Rx cksum flags on IP options packets Olivier Matz
2021-04-30 14:48 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-06-08 10:13 ` Andrew Rybchenko
2021-06-08 12:29 ` Olivier Matz
2021-06-08 12:34 ` Andrew Rybchenko
2021-06-08 12:49 ` Olivier Matz
2021-06-08 13:57 ` Andrew Rybchenko
2021-06-08 14:30 ` Olivier Matz
2021-04-27 13:57 ` [dpdk-dev] [PATCH 2/4] net/tap: fix Rx cksum flags on TCP packets Olivier Matz
2021-06-08 10:18 ` Andrew Rybchenko
2021-04-27 13:57 ` [dpdk-dev] [PATCH 3/4] net: introduce functions to verify L4 checksums Olivier Matz
2021-04-27 15:02 ` Morten Brørup
2021-04-27 15:07 ` Morten Brørup
2021-04-28 12:21 ` Olivier Matz
2021-04-28 12:42 ` Morten Brørup
2021-04-30 15:42 ` Ferruh Yigit
2021-06-08 10:23 ` Andrew Rybchenko
2021-06-08 12:29 ` Olivier Matz
2021-06-08 12:39 ` Andrew Rybchenko
2021-06-25 15:38 ` Ferruh Yigit
2021-04-27 13:57 ` [dpdk-dev] [PATCH 4/4] test/cksum: new test for L3/L4 checksum API Olivier Matz
2021-06-30 13:51 ` Olivier Matz [this message]
2021-06-30 13:51 ` [dpdk-dev] [PATCH v2 1/4] net/tap: fix Rx cksum flags on IP options packets Olivier Matz
2021-06-30 13:51 ` [dpdk-dev] [PATCH v2 2/4] net/tap: fix Rx cksum flags on TCP packets Olivier Matz
2021-06-30 13:51 ` [dpdk-dev] [PATCH v2 3/4] net: introduce functions to verify L4 checksums Olivier Matz
2021-06-30 13:51 ` [dpdk-dev] [PATCH v2 4/4] test/cksum: new test for L3/L4 checksum API Olivier Matz
2021-07-01 9:28 ` [dpdk-dev] [PATCH v2 0/4] net/tap: fix Rx cksum Andrew Rybchenko
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=20210630135158.8108-1-olivier.matz@6wind.com \
--to=olivier.matz@6wind.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=guohongzhi1@huawei.com \
--cc=keith.wiles@intel.com \
--cc=mb@smartsharesystems.com \
--cc=thomas@monjalon.net \
/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).