From: "Xu, Ke1" <ke1.xu@intel.com>
To: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>, "Xu, Ke1" <ke1.xu@intel.com>
Subject: RE: [PATCH 0/4] support UDP fragmentation offload
Date: Wed, 24 May 2023 03:33:45 +0000 [thread overview]
Message-ID: <PH7PR11MB6056F6812E70C6F60ABB0DBDD3419@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230413053337.4190536-1-zhichaox.zeng@intel.com>
> From: Zhichao Zeng <zhichaox.zeng@intel.com>
> Sent: Thursday, April 13, 2023 1:34 PM
> To: dev@dpdk.org
> Cc: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> Subject: [PATCH 0/4] support UDP fragmentation offload
>
> This patch set supports UDP fragmentation offload for ice and iavf.
>
> Zhichao Zeng (4):
> net: calculate correct UDP pseudo header for UFO
> app/testpmd: support UFO in checksum engine
> net/ice: enable UDP fragmentation offload
> net/iavf: enable UDP fragmentation offload
>
Verified and Passed.
Two extra issues exists found blocking very limited part of validation.
1. On QEMU DCF not able to enable rx_vxlan.
2. IPv6 Tunneled UDP packets triggers MDD event.
Tested-by: Ke Xu <ke1.xu@intel.com>
> app/test-pmd/csumonly.c | 17 ++++++++++++-----
> drivers/net/iavf/iavf_rxtx.c | 2 +-
> drivers/net/iavf/iavf_rxtx.h | 2 ++
> drivers/net/ice/ice_rxtx.c | 15 ++++++++++++---
> lib/net/rte_ip.h | 4 ++--
> lib/net/rte_net.h | 5 +++--
> 6 files changed, 32 insertions(+), 13 deletions(-)
>
> --
> 2.25.1
prev parent reply other threads:[~2023-05-24 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 5:33 Zhichao Zeng
2023-05-24 3:33 ` Xu, Ke1 [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=PH7PR11MB6056F6812E70C6F60ABB0DBDD3419@PH7PR11MB6056.namprd11.prod.outlook.com \
--to=ke1.xu@intel.com \
--cc=dev@dpdk.org \
--cc=zhichaox.zeng@intel.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).