DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: Junfeng Guo <junfeng.guo@intel.com>, <qi.z.zhang@intel.com>,
	<jingjing.wu@intel.com>, <beilei.xing@intel.com>
Cc: <dev@dpdk.org>, Xiao Wang <xiao.w.wang@intel.com>
Subject: Re: [PATCH v2] app/testpmd: add throughput stats for forward streams
Date: Thu, 16 Jun 2022 22:09:50 +0530	[thread overview]
Message-ID: <416d56d6-4ef2-0b29-9a18-3928026905fc@intel.com> (raw)
In-Reply-To: <20220606093945.2978915-1-junfeng.guo@intel.com>

Hi Junfeng,

Thanks for the patch.


On 6/6/2022 3:09 PM, Junfeng Guo wrote:
> 1. add throughput statistics (in pps) for forward streams.
> 2. display the forward statistics for every forward stream.
>
> v2:
> add parameter descriptions and fix commit title.
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
> ---
>
We do have per port Rx/Tx pps in display stats.
For per forward stream we can enable "--record-burst-stats".
With it we can get per fwd stream Rx/Tx pps.

Please check if this patch is adding any additional functionality.

<snip>


  reply	other threads:[~2022-06-16 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  8:27 [PATCH] testpmd: optimize forward stream statistics Junfeng Guo
2022-05-31 15:27 ` Andrew Rybchenko
2022-06-06  9:02   ` Guo, Junfeng
2022-06-01  8:46 ` Singh, Aman Deep
2022-06-06  9:00   ` Guo, Junfeng
2022-06-06  9:39 ` [PATCH v2] app/testpmd: add throughput stats for forward streams Junfeng Guo
2022-06-16 16:39   ` Singh, Aman Deep [this message]
2022-08-11  6:57     ` Guo, Junfeng
2022-08-16  9:32       ` Ferruh Yigit
2022-08-18  6:57         ` Guo, Junfeng

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=416d56d6-4ef2-0b29-9a18-3928026905fc@intel.com \
    --to=aman.deep.singh@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=junfeng.guo@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=xiao.w.wang@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).