From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] introduce dev_ops to get extended statistics of a device
Date: Wed, 23 Jul 2014 14:28:52 +0200 [thread overview]
Message-ID: <1406118534-6169-1-git-send-email-olivier.matz@6wind.com> (raw)
The generic statistics structure is getting bigger as new statistics are
added in specific devices. For instance, fdir, tx_pause or loopback
stats do not apply on virtual devices. It won't be possible to add every
specific statistics in this generic stats structure, but on the other
hand these specific statistics are useful for debugging purpose.
This 2 patches introduces xstats_get() and xstats_reset() in
dev_ops. When registered by a device, it can be used to provide
arbitrary statistics that are identified by a name, as done by eththool
in kernel.
After that, some statistics could be moved from the generic structure to
this new framework, but it will be part of another patch series as it
should be discussed first.
Olivier Matz (2):
ethdev: add a new rte_eth_xstats_get method to retrieve extended
statistics
testpmd: add a new command to get the extended statistics of a port
app/test-pmd/cmdline.c | 22 +++++--
app/test-pmd/config.c | 34 +++++++++++
app/test-pmd/testpmd.h | 2 +
lib/librte_ether/rte_ethdev.c | 137 ++++++++++++++++++++++++++++++++++++++++++
lib/librte_ether/rte_ethdev.h | 60 +++++++++++++++++-
5 files changed, 247 insertions(+), 8 deletions(-)
--
2.0.1
next reply other threads:[~2014-07-23 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 12:28 Olivier Matz [this message]
2014-07-23 12:28 ` [dpdk-dev] [PATCH 1/2] ethdev: add a new rte_eth_xstats_get method to retrieve extended statistics Olivier Matz
2014-07-23 12:28 ` [dpdk-dev] [PATCH 2/2] testpmd: add a new command to get the extended statistics of a port Olivier Matz
2014-07-23 18:41 ` [dpdk-dev] [PATCH 0/2] introduce dev_ops to get extended statistics of a device Richardson, Bruce
2014-09-23 15:49 ` Thomas Monjalon
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=1406118534-6169-1-git-send-email-olivier.matz@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.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).