From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: oulijun <oulijun@huawei.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: Re: [dpdk-dev] [PATCH 3/3] app/testpmd: use of Rx/Tx in testpmd
Date: Tue, 23 Mar 2021 07:59:57 +0000 [thread overview]
Message-ID: <38434ecb2ba645358a7c3496797538ec@intel.com> (raw)
In-Reply-To: <fd2e8ea1-b2c7-fa7d-d317-0362704b3ae0@huawei.com>
> -----Original Message-----
> From: oulijun <oulijun@huawei.com>
> Sent: 2021年3月23日 15:52
> To: Tu, Lijuan <lijuan.tu@intel.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Li, Xiaoyun <xiaoyun.li@intel.com>; Yigit,
> Ferruh <ferruh.yigit@intel.com>
> Cc: dev@dpdk.org; linuxarm@openeuler.org
> Subject: Re: [dpdk-dev] [PATCH 3/3] app/testpmd: use of Rx/Tx in testpmd
>
>
>
> 在 2021/3/23 15:46, Tu, Lijuan 写道:
> >
> >
> >> -----Original Message-----
> >> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> >> Sent: 2021年3月23日 15:25
> >> To: Li, Xiaoyun <xiaoyun.li@intel.com>; Lijun Ou
> >> <oulijun@huawei.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Tu,
> >> Lijuan <lijuan.tu@intel.com>
> >> Cc: dev@dpdk.org; linuxarm@openeuler.org
> >> Subject: Re: [dpdk-dev] [PATCH 3/3] app/testpmd: use of Rx/Tx in
> >> testpmd
> >>
> >> On 3/23/21 6:17 AM, Li, Xiaoyun wrote:
> >>> Hi
> >>>
> >>>> -----Original Message-----
> >>>> From: Lijun Ou <oulijun@huawei.com>
> >>>> Sent: Friday, March 5, 2021 18:22
> >>>> To: Yigit, Ferruh <ferruh.yigit@intel.com>
> >>>> Cc: Li, Xiaoyun <xiaoyun.li@intel.com>; dev@dpdk.org;
> >>>> linuxarm@openeuler.org
> >>>> Subject: [PATCH 3/3] app/testpmd: use of Rx/Tx in testpmd
> >>>>
> >>>> From: Hongbo Zheng <zhenghongbo3@huawei.com>
> >>>>
> >>>> In testpmd, when we input "show config rxtx", we can see like this:
> >>>>
> >>>> 1: testpmd> show config rxtx
> >>>> 2: io packet forwarding packets/burst=32
> >>>> 3: nb forwarding cores=1 - nb forwarding ports=1
> >>>> 4: port 0: RX queue number: 1 Tx queue number: 1
> >>>> 5: Rx offloads=0x0 Tx offloads=0x10000
> >>>> 6: RX queue: 0
> >>>> 7: RX desc=1024 - RX free threshold=32
> >>>> 8: RX threshold registers: pthresh=0 hthresh=0 wthresh=0
> >>>> 9: RX Offloads=0x0
> >>>> 10: TX queue: 0
> >>>> 11: TX desc=1024 - TX free threshold=928
> >>>> 12: TX threshold registers: pthresh=0 hthresh=0 wthresh=0
> >>>> 13: TX offloads=0x10000 - TX RS bit threshold=32
> >>>>
> >>>> We can see RX/Rx/TX/Tx is mixed used. Also in other places in
> >>>> testpmd, RX/Rx/TX/Tx is mixed used.
> >>>>
> >>>> This patch fix the mixed use of RX/Rx/TX/Tx in testpmd by change to
> >>>> unified use Rx/Tx.
> >>>
> >>> The commit log is too redundant. The following is enough to explain
> >>> what this
> >> patch does:
> >>> RX/TX and Rx/Tx are mixed used in testpmd print and comments. This
> >>> patch
> >> unifies them as Rx/Tx.
> >>>
> >>> Except this, the patch looks good to me.
> >>>
> >>> But one big concern, this patch will break all of the CI tests
> >>> because the DTS
> >> scripts check if the results are the same as expected and this patch
> >> change a lot of the print.
> >>> So I think the DTS maintainer needs to be aware of this.
> >>
> >> I think test dpdk-testpmd output is a part of API. Of course, it is
> >> not an API, but such cosmetic changes in output will be much more painful
> than API changes.
> >> Output parsers will simply stop to work. I think such changes should
> >> go through the deprecation process.
> >>
> >> Of course, it would be useful to change comments and may be even
> >> error log messages right now, but not commands output.
> >>
> >>>
> >>> +Lijuan DTS maintainer
> >
> > It has big impact with CI system, most of test cases depended on the testpmd
> output, if changed, our CI system will be broken, Is it really worth it ?
> >
> I think it's necessary to keep the style consistent and to constrain everyone to do
> so in the future.However, if the DTS changes greatly, I think it is possible to
> require the new print to be consistent and the historical part to remain
> unchanged.Because the uniform change is also Xiaoyun's suggestion, we think
> the opinion is reasonable, but we are not sure how much it will affect DTS.
If that, I think it should go to DPDK tech board, shall we only unify testpmd or consider libraries and other applications.
> >>>
> >>> And please separate this patch with the other twos. Don't mix them
> >>> in one
> >> patchset. It's not for the same purpose.
> >>>
> >>>>
> >>>> Signed-off-by: Hongbo Zheng <zhenghongbo3@huawei.com>
> >>>> Signed-off-by: Lijun Ou <oulijun@huawei.com>
> >>>> ---
> >>>> V1->V2:
> >>>> - fix all RX/TX
> >>>> - rename patch title
> >>>> ---
> >>>> app/test-pmd/cmdline.c | 104 ++++++++++++++++++------------------
> >>>> app/test-pmd/config.c | 128 ++++++++++++++++++++++------------------
> ---
> >> --
> >>>> app/test-pmd/csumonly.c | 22 ++++----
> >>>> app/test-pmd/icmpecho.c | 2 +-
> >>>> app/test-pmd/ieee1588fwd.c | 18 +++----
> >>>> app/test-pmd/parameters.c
> >>>> | 50 +++++++++---------
> >>>> app/test-pmd/testpmd.c | 120 +++++++++++++++++++++------------------
> ---
> >>>> app/test-pmd/testpmd.h | 28 +++++-----
> >>>> app/test-pmd/txonly.c | 2 +-
> >>>> 9 files changed, 237 insertions(+), 237 deletions(-)
> >>>> --
> >>>> 2.7.4
next prev parent reply other threads:[~2021-03-23 8:00 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 10:22 [dpdk-dev] [PATCH 0/3] Fixes for testpmd Lijun Ou
2021-03-05 10:22 ` [dpdk-dev] [PATCH 1/3] app/testpmd: fix forwarding configuration when DCB test Lijun Ou
2021-03-23 8:55 ` Li, Xiaoyun
2021-03-23 14:17 ` oulijun
2021-03-23 14:17 ` oulijun
2021-03-24 1:51 ` Li, Xiaoyun
2021-04-10 1:12 ` Ferruh Yigit
2021-04-10 2:53 ` oulijun
2021-03-23 14:18 ` oulijun
2021-03-24 2:03 ` Li, Xiaoyun
2021-03-24 13:40 ` [dpdk-dev] [Linuxarm] " oulijun
2021-03-25 2:21 ` Li, Xiaoyun
2021-03-27 3:53 ` oulijun
2021-04-10 0:56 ` Ferruh Yigit
2021-04-10 2:58 ` oulijun
2021-04-12 7:52 ` Ferruh Yigit
2021-04-12 12:20 ` oulijun
2021-03-05 10:22 ` [dpdk-dev] [PATCH 2/3] app/testpmd: remove forwarding config from parsing Rx and Tx Lijun Ou
2021-03-23 7:50 ` Li, Xiaoyun
2021-03-24 1:00 ` oulijun
2021-03-24 1:44 ` Li, Xiaoyun
2021-03-25 3:03 ` oulijun
2021-03-29 1:53 ` Li, Xiaoyun
2021-04-02 1:44 ` oulijun
2021-04-02 2:33 ` Li, Xiaoyun
2021-04-09 6:09 ` [dpdk-dev] [Linuxarm] " oulijun
2021-04-09 7:08 ` Li, Xiaoyun
2021-04-10 3:02 ` oulijun
2021-04-12 10:35 ` [dpdk-dev] " Ferruh Yigit
2021-04-12 12:20 ` oulijun
2021-03-05 10:22 ` [dpdk-dev] [PATCH 3/3] app/testpmd: use of Rx/Tx in testpmd Lijun Ou
2021-03-23 3:12 ` Li, Xiaoyun
2021-03-23 3:17 ` Li, Xiaoyun
2021-03-23 7:25 ` Andrew Rybchenko
2021-03-23 7:46 ` Tu, Lijuan
2021-03-23 7:51 ` oulijun
2021-03-23 7:58 ` Li, Xiaoyun
2021-03-23 10:42 ` Ferruh Yigit
2021-03-23 7:59 ` Tu, Lijuan [this message]
2021-03-20 1:19 ` [dpdk-dev] [PATCH 0/3] Fixes for testpmd Min Hu (Connor)
2021-04-20 7:31 ` [dpdk-dev] [PATCH V2 0/7] modifications about DCB forwarding configuration Huisong Li
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 1/7] app/testpmd: fix forward lcores number when DCB test Huisong Li
2021-04-27 9:20 ` Li, Xiaoyun
2021-04-27 13:49 ` Huisong Li
2021-04-28 2:13 ` Li, Xiaoyun
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 2/7] app/testpmd: fix DCB forwarding configuration Huisong Li
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 3/7] app/testpmd: fix a segment fault when DCB test Huisong Li
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 4/7] app/testpmd: add check for support of reporting DCB info Huisong Li
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 5/7] app/testpmd: move position of verifying DCB test Huisong Li
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 6/7] app/testpmd: add forwarding config in start port Huisong Li
2021-04-20 7:32 ` [dpdk-dev] [PATCH V2 7/7] app/testpmd: remove redundant fwd streams initialization Huisong Li
2021-04-20 7:35 ` [dpdk-dev] [PATCH 0/3] Fixes for testpmd Huisong Li
2021-04-20 9:00 ` [dpdk-dev] [PATCH V3 0/7] modifications about DCB forwarding configuration Huisong Li
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 1/7] app/testpmd: fix forward lcores number when DCB test Huisong Li
2021-04-27 10:18 ` Li, Xiaoyun
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 2/7] app/testpmd: fix DCB forwarding configuration Huisong Li
2021-04-27 10:59 ` Li, Xiaoyun
2021-04-27 14:13 ` Huisong Li
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 3/7] app/testpmd: fix a segment fault when DCB test Huisong Li
2021-04-27 11:19 ` Li, Xiaoyun
2021-04-27 14:10 ` Huisong Li
2021-04-28 2:02 ` Li, Xiaoyun
2021-04-28 2:26 ` Huisong Li
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 4/7] app/testpmd: add check for support of reporting DCB info Huisong Li
2021-04-27 11:26 ` Li, Xiaoyun
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 5/7] app/testpmd: move position of verifying DCB test Huisong Li
2021-04-27 11:33 ` Li, Xiaoyun
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 6/7] app/testpmd: add forwarding config in start port Huisong Li
2021-04-27 11:43 ` Li, Xiaoyun
2021-04-28 2:14 ` Huisong Li
2021-04-20 9:01 ` [dpdk-dev] [PATCH V3 7/7] app/testpmd: remove redundant fwd streams initialization Huisong Li
2021-04-27 11:50 ` Li, Xiaoyun
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 0/7] modifications about DCB forwarding configuration Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 1/7] app/testpmd: fix forward lcores number when DCB test Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 2/7] app/testpmd: fix DCB forwarding configuration Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 3/7] app/testpmd: fix a segment fault when DCB test Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 4/7] app/testpmd: add check for support of reporting DCB info Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 5/7] app/testpmd: move position of verifying DCB test Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 6/7] app/testpmd: add forwarding configuration when config DCB Huisong Li
2021-04-28 6:40 ` [dpdk-dev] [PATCH V4 7/7] app/testpmd: remove redundant fwd streams initialization Huisong Li
2021-04-28 7:01 ` [dpdk-dev] [PATCH V4 0/7] modifications about DCB forwarding configuration Li, Xiaoyun
2021-04-29 16:13 ` 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=38434ecb2ba645358a7c3496797538ec@intel.com \
--to=lijuan.tu@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linuxarm@openeuler.org \
--cc=oulijun@huawei.com \
--cc=xiaoyun.li@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).