patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] common/idpf: fix Tx checksum offload
Date: Fri, 22 Sep 2023 08:23:38 +0000	[thread overview]
Message-ID: <BN0PR11MB57128B0FA646D0D8EEB705F0FDFFA@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230922152935.146302-1-beilei.xing@intel.com>

> -----Original Message-----
> From: beilei.xing@intel.com <beilei.xing@intel.com>
> Sent: Friday, September 22, 2023 11:30 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>
> Cc: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>; stable@dpdk.org
> Subject: [PATCH] common/idpf: fix Tx checksum offload
>
> From: Beilei Xing <beilei.xing@intel.com>
>
> For multi-segment packets, the Tx checksum offload doesn't work except the
> last segment, because other segments don't enable HW checksum offload
> successfully.
>
> Fixes: ef47d95e9031 ("net/idpf: fix TSO")
> Fixes: 8c6098afa075 ("common/idpf: add Rx/Tx data path")
> Cc: stable@dpdk.org
>
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>
> ---
Verified scalar path + single queue and split queue, tested pass for TX checksum on TSO offload.
Tested-by: Zhimin Huang <zhiminx.huang@intel.com >

  reply	other threads:[~2023-09-22  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 15:29 beilei.xing
2023-09-22  8:23 ` Huang, ZhiminX [this message]
2023-09-26  2:53   ` 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=BN0PR11MB57128B0FA646D0D8EEB705F0FDFFA@BN0PR11MB5712.namprd11.prod.outlook.com \
    --to=zhiminx.huang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=stable@dpdk.org \
    /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).