From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
dev@dpdk.org, Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] failsafe: implement xstats
Date: Fri, 8 Nov 2019 18:13:21 +0000 [thread overview]
Message-ID: <cc866334-2cf6-2e1d-26b0-e9f8a2ec6a0d@intel.com> (raw)
In-Reply-To: <20191101201255.4853-3-stephen@networkplumber.org>
On 11/1/2019 8:12 PM, Stephen Hemminger wrote:
> Add support for extended statistics in failsafe driver.
> Reports detailed statistics for each sub device.
>
> Example:
>
> testpmd> show port xstats 1
> rx_good_packets: 0
> tx_good_packets: 0
> rx_good_bytes: 0
> tx_good_bytes: 0
> rx_missed_errors: 0
> rx_errors: 0
> tx_errors: 0
> rx_mbuf_allocation_errors: 0
> rx_q0packets: 0
> rx_q0bytes: 0
> rx_q0errors: 0
> tx_q0packets: 0
> tx_q0bytes: 0
> rx_sub0_good_packets: 0
> tx_sub0_good_packets: 0
> ...
> rx_sub1_good_packets: 0
> tx_sub1_good_packets: 0
> rx_sub1_good_bytes: 0
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Hi Stephen, Geatan,
What do you think about adding Stephen as additional failsafe maintainer?
next prev parent reply other threads:[~2019-11-08 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 20:12 [dpdk-dev] [PATCH 0/2] xstats related patches Stephen Hemminger
2019-11-01 20:12 ` [dpdk-dev] [PATCH 1/2] app/testpmd: block xstats for hidden ports Stephen Hemminger
2019-11-04 11:25 ` Iremonger, Bernard
2019-11-01 20:12 ` [dpdk-dev] [PATCH 2/2] failsafe: implement xstats Stephen Hemminger
2019-11-08 18:13 ` Ferruh Yigit [this message]
2019-11-08 18:26 ` [dpdk-dev] [PATCH 0/2] xstats related patches Ferruh Yigit
-- strict thread matches above, loose matches on Subject: below --
2019-06-26 22:21 [dpdk-dev] [PATCH 0/2] failsafe: add xstats Stephen Hemminger
2019-06-26 22:21 ` [dpdk-dev] [PATCH 2/2] failsafe: implement xstats Stephen Hemminger
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=cc866334-2cf6-2e1d-26b0-e9f8a2ec6a0d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=stephen@networkplumber.org \
/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).