DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zeng, ZhichaoX" <zhichaox.zeng@intel.com>
To: "Matz, Olivier" <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Zhou, YidingX" <yidingx.zhou@intel.com>,
	"Jiang, YuX" <yux.jiang@intel.com>
Subject: RE: [PATCH] lib/net: support UDP pseudo-header for UFO
Date: Mon, 13 Feb 2023 10:22:34 +0000	[thread overview]
Message-ID: <CO6PR11MB5602E7EB787A30AE709475A0F1DD9@CO6PR11MB5602.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Y+ZEg7QzhOMJzIm8@platinum>

Hi Olivier,

Thanks for your comments. 

Yes, this patch is to support the UDP fragmentation offload feature
in the iavf driver, which is planned to be fully supported in 23.07.

It's my fault for not clarifying the details. In addition, is it acceptable
to add the UDP_SEG flag separately now?

If it's acceptable, I'll resubmit v2 and add more details into the log.
If not, I'll submit it later with the rest code of the UFO feature.

BR
Zhichao

> -----Original Message-----
> From: Olivier Matz <olivier.matz@6wind.com>
> Sent: Friday, February 10, 2023 9:20 PM
> To: Zeng, ZhichaoX <zhichaox.zeng@intel.com>
> Cc: dev@dpdk.org; Zhou, YidingX <yidingx.zhou@intel.com>
> Subject: Re: [PATCH] lib/net: support UDP pseudo-header for UFO
> 
> Hello Zhichao,
> 
> Sorry for the delayed response.
> 
> >
> 
> Can you give some more detail about how rte_ipv4_phdr_cksum() is called in
> your
> use-case? (what driver, what libs, what use-case)
> 
> Currently, I see that only the iavf driver supports udp-segmented packets.
> The
> lib/vhost is also able to pass the offload information to the virtio ring.
> 
> For me, the mbufs that have offload flags and that are being transmitted to a
> driver should use the rte_eth_tx_prepare() API. This function will (among
> other
> things) update the required checksums in the packet when Tx offload is set.
> 
> Most drivers call rte_net_intel_cksum_flags_prepare() in their
> tx_pkt_prepare
> callback, so I suspect this function has to be updated. Note that updating it
> may have an impact on its user that supports UDP_SEG (lib/vhost and
> driver/net/iavf).
> 
> I'm not saying that the patch is wrong, but I would like to better understand
> why you need it.
> 
> Regards,
> Olivier

      reply	other threads:[~2023-02-13 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12  9:26 Zhichao Zeng
2023-02-08 10:35 ` Zeng, ZhichaoX
2023-02-10 13:20 ` Olivier Matz
2023-02-13 10:22   ` Zeng, ZhichaoX [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=CO6PR11MB5602E7EB787A30AE709475A0F1DD9@CO6PR11MB5602.namprd11.prod.outlook.com \
    --to=zhichaox.zeng@intel.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=yidingx.zhou@intel.com \
    --cc=yux.jiang@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).