DPDK patches and discussions
 help / color / mirror / Atom feed
From: Huisong Li <lihuisong@huawei.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <ferruh.yigit@amd.com>,
	<aman.deep.singh@intel.com>, <yuying.zhang@intel.com>,
	<zhichaox.zeng@intel.com>, <lihuisong@huawei.com>
Subject: [PATCH v3 0/2] app/testpmd: fix UDP cksum error for UFO enable
Date: Tue, 7 Nov 2023 12:11:15 +0800	[thread overview]
Message-ID: <20231107041117.23285-1-lihuisong@huawei.com> (raw)
In-Reply-To: <20230728021310.15970-1-lihuisong@huawei.com>

1. remove useless code.
2. fix UDP cksum error for UFO enable.
For detail message, please see the commit log.

---
 v3:
  - separate the useless code from patch v2.
  - fix some comments and use 'printf' to replace 'fprintf'.

 v2: add handle for tunnel TSO offload in process_inner_cksums

Huisong Li (2):
  app/testpmd: remove useless code for TSO setting command
  app/testpmd: fix UDP cksum error for UFO enable

 app/test-pmd/cmdline.c  | 44 ++++++++++++++++++++---------------------
 app/test-pmd/csumonly.c | 11 +++++++++--
 2 files changed, 30 insertions(+), 25 deletions(-)

-- 
2.33.0


  parent reply	other threads:[~2023-11-07  4:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  2:13 [PATCH] " Huisong Li
2023-08-02  2:55 ` [PATCH v2] " Huisong Li
2023-10-20  3:38   ` lihuisong (C)
2023-10-27  6:15   ` fengchengwen
2023-11-03  1:31   ` Ferruh Yigit
2023-11-03  9:09     ` lihuisong (C)
2023-11-03 10:42       ` Ferruh Yigit
2023-11-06  4:13         ` lihuisong (C)
2023-11-06 10:09           ` Ferruh Yigit
2023-11-06 12:29             ` lihuisong (C)
2023-11-07  4:11 ` Huisong Li [this message]
2023-11-07  4:11   ` [PATCH v3 1/2] app/testpmd: remove useless code for TSO setting command Huisong Li
2023-11-07  4:11   ` [PATCH v3 2/2] app/testpmd: fix UDP cksum error for UFO enable Huisong Li
2023-11-07  9:54   ` [PATCH v3 0/2] " Ferruh Yigit

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=20231107041117.23285-1-lihuisong@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=thomas@monjalon.net \
    --cc=yuying.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).