DPDK patches and discussions
 help / color / mirror / Atom feed
From: Huisong Li <lihuisong@huawei.com>
To: <dev@dpdk.org>, <ferruh.yigit@amd.com>
Cc: <andrew.rybchenko@oktetlabs.ru>, <liuyonglong@huawei.com>,
	<lihuisong@huawei.com>
Subject: [PATCH v2 0/3] app/testpmd: fix the command to set tunnel TSO
Date: Sat, 11 Nov 2023 12:59:40 +0800	[thread overview]
Message-ID: <20231111045944.46378-1-lihuisong@huawei.com> (raw)
In-Reply-To: <20231110081925.14142-1-lihuisong@huawei.com>

Please see each patch in the series for detail.

---
 -v2: fix the position of check code based on Ferruh's comments

Huisong Li (3):
  app/testpmd: fix random value to set tunnel TSO
  app/testpmd: add the explicit check for tunnel TSO offload
  app/testpmd: fix unnecessary change when set tunnel TSO

 app/test-pmd/cmdline.c | 93 ++++++++++++++++++++----------------------
 1 file changed, 44 insertions(+), 49 deletions(-)

-- 
2.33.0


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10  8:19 [PATCH v1 " Huisong Li
2023-11-10  8:19 ` [PATCH v1 1/3] app/testpmd: fix random value " Huisong Li
2023-11-10 11:42   ` Ivan Malov
2023-11-11  1:17     ` lihuisong (C)
2023-11-11  3:22       ` Ferruh Yigit
2023-11-10  8:19 ` [PATCH v1 2/3] app/testpmd: add the explicit check for tunnel TSO offload Huisong Li
2023-11-11  3:30   ` Ferruh Yigit
2023-11-11  4:27     ` lihuisong (C)
2023-11-10  8:19 ` [PATCH v1 3/3] app/testpmd: fix unnecessary change when set tunnel TSO Huisong Li
2023-11-11  3:37   ` Ferruh Yigit
2023-11-11  4:28     ` lihuisong (C)
2023-11-11  4:59 ` Huisong Li [this message]
2023-11-11  4:59   ` [PATCH v2 1/3] app/testpmd: fix random value to " Huisong Li
2023-11-11  4:59   ` [PATCH v2 2/3] app/testpmd: add the explicit check for tunnel TSO offload Huisong Li
2023-11-11  4:59   ` [PATCH v2 3/3] app/testpmd: fix unnecessary change when set tunnel TSO Huisong Li
2023-11-11  5:59   ` [PATCH v2 0/3] app/testpmd: fix the command to " 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=20231111045944.46378-1-lihuisong@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=liuyonglong@huawei.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).