DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, Ke1" <ke1.xu@intel.com>
To: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Xu, Ke1" <ke1.xu@intel.com>
Subject: RE: [PATCH 4/4] net/iavf: enable UDP fragmentation offload
Date: Wed, 24 May 2023 05:20:42 +0000	[thread overview]
Message-ID: <PH7PR11MB605684BDAEBBCC4FC3623EF5D3419@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230413053506.4191340-1-zhichaox.zeng@intel.com>

> From: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> Sent: Thursday, April 13, 2023 1:35 PM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Xu, Ke1 <ke1.xu@intel.com>; Zeng,
> ZhichaoX <zhichaox.zeng@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>
> Subject: [PATCH 4/4] net/iavf: enable UDP fragmentation offload
> 
> This commit enables transmit segmentation offload for UDP, including both
> non-tunneled and tunneled packets.
> 
> The command "tso set <tso_segsz> <port_id>" or "tunnel_tso set <tso_segsz>
> <port_id>" is used to enable UFO.
> 
> Signed-off-by: Zhichao Zeng <zhichaox.zeng@intel.com>

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>

> ---
>  drivers/net/iavf/iavf_rxtx.c | 2 +-
>  drivers/net/iavf/iavf_rxtx.h | 2 ++
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 


  reply	other threads:[~2023-05-24  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13  5:35 Zhichao Zeng
2023-05-24  5:20 ` Xu, Ke1 [this message]
2023-06-07  1:00   ` Zhang, Qi Z

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=PH7PR11MB605684BDAEBBCC4FC3623EF5D3419@PH7PR11MB6056.namprd11.prod.outlook.com \
    --to=ke1.xu@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=qi.z.zhang@intel.com \
    --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).