DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, Ke1" <ke1.xu@intel.com>
To: "He, ShiyangX" <shiyangx.he@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhou, YidingX" <yidingx.zhou@intel.com>,
	"He, ShiyangX" <shiyangx.he@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Subject: RE: [PATCH v2] net/ice:fix tunnel packet TX descriptor error
Date: Wed, 14 Jun 2023 01:26:09 +0000	[thread overview]
Message-ID: <PH7PR11MB6056E4EF748D010BB496C631D35AA@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230608101904.65340-1-shiyangx.he@intel.com>

> From: Shiyang He <shiyangx.he@intel.com>
> Sent: Thursday, June 8, 2023 6:19 PM
> To: dev@dpdk.org
> Cc: Zhou, YidingX <yidingx.zhou@intel.com>; He, ShiyangX
> <shiyangx.he@intel.com>; stable@dpdk.org; Yang, Qiming
> <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>
> Subject: [PATCH v2] net/ice:fix tunnel packet TX descriptor error
> 
> The TX descriptor of tunnel packet filled incorrectly due to the MACLEN is not
> set.
> 
> This patch fixes this issue by setting MACLEN to correctly fill the TX descriptor.
> 
> Fixes: bd70c451532c ("net/ice: support Tx checksum offload for tunnel")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Shiyang He <shiyangx.he@intel.com>

Verified passed.

Tested-by: Ke Xu <ke1.xu@intel.com>

> ---
>  drivers/net/ice/ice_rxtx.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 


      parent reply	other threads:[~2023-06-14  1:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 15:36 [PATCH] app/testpmd: fix IPv6 tunnel packet checksum error Shiyang He
2023-06-01 22:09 ` Ferruh Yigit
2023-06-06  9:39   ` He, ShiyangX
2023-06-08 10:19 ` [PATCH v2] net/ice:fix tunnel packet TX descriptor error Shiyang He
2023-06-12 12:55   ` Zhang, Qi Z
2023-06-14  1:26   ` 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=PH7PR11MB6056E4EF748D010BB496C631D35AA@PH7PR11MB6056.namprd11.prod.outlook.com \
    --to=ke1.xu@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=shiyangx.he@intel.com \
    --cc=stable@dpdk.org \
    --cc=yidingx.zhou@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).