From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "David Harton (dharton)" <dharton@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Future Direction for rte_eth_stats_get()
Date: Fri, 22 Jan 2016 15:48:08 +0100 [thread overview]
Message-ID: <1670837.tJHuUIkoht@xps13> (raw)
In-Reply-To: <ce025b0121ff465a9abcc604c437ff59@XCH-RCD-016.cisco.com>
+ Harry
2016-01-22 14:40, David Harton:
> Hi Maryam,
>
> I'm not dictating they be re-added (although adding would be nice) but more important I'm trying to express an application view point rather than a driver view point.
>
> I completely understand how a driver wants to be able to advertise all the stats they want to advertise to help them debug their issues (i.e. xstats). Yet, I'm very interested in DPDK providing a driver agnostic method of advertising well-defined stats.
xstats are driver agnostic and have a well-defined naming scheme.
> For example, what if there was a kind of "stats registry" composed of ID and name. It would work similar to xtats except instead of advertising strings only the "get" API would return ID/count pairs. If the application wishes to use the DPDK provided string they can call another API to get the stat string via the ID. These IDs would be well-defined clearly explaining what the count represent. This way the strings for counts will be uniform across drivers and also make it clear to the users what the counts truly represent and the application could obtain stats from any driver in a driver agnostic manner.
I don't understand how adding another indirection (an ID matching a string)
would help?
I have the feeling you want a list of possible statistics, right?
PS: please avoid top posting
next prev parent reply other threads:[~2016-01-22 14:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 17:18 David Harton (dharton)
2016-01-22 11:07 ` Tahhan, Maryam
2016-01-22 13:40 ` David Harton (dharton)
2016-01-22 14:18 ` Tahhan, Maryam
2016-01-22 14:40 ` David Harton (dharton)
2016-01-22 14:48 ` Thomas Monjalon [this message]
2016-01-22 15:22 ` Van Haaren, Harry
2016-01-22 15:53 ` Jay Rolette
2016-01-22 16:04 ` David Harton (dharton)
2016-01-22 16:37 ` Thomas Monjalon
2016-01-22 16:41 ` Van Haaren, Harry
2016-01-22 19:26 ` David Harton (dharton)
2016-01-28 9:37 ` Van Haaren, Harry
2016-02-01 16:47 ` David Harton (dharton)
2016-02-01 21:23 ` Matthew Hall
2016-02-02 11:40 ` Van Haaren, Harry
2016-02-05 21:16 ` David Harton (dharton)
2016-02-19 8:59 ` Tahhan, Maryam
2016-01-22 14:44 ` Thomas Monjalon
2016-01-22 14:48 ` Tahhan, Maryam
2016-01-22 15:02 ` Igor Ryzhov
2016-01-22 20:48 ` Matthew Hall
2016-02-02 12:44 ` Tahhan, Maryam
2016-02-02 13:47 ` Kyle Larose
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=1670837.tJHuUIkoht@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=dharton@cisco.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).