[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Thomas Monjalon
2015-10-29 09:57, Kyle Larose: > On Thu, Oct 29, 2015 at 9:10 AM, Thomas Monjalon > wrote: > > > I don't understand. > > The basic statistics are provided in a common API. > > The other ones are not available in every NICs and can only be interpreted > > while knowing the device. So what is the n

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Thomas Monjalon
2015-10-29 08:55, Kyle Larose: > Ultimately the issue we are trying to solve is that there is no device > independent way to get any detailed statistics from NICs controlled by > DPDK. These statistics are quite useful, not just for diagnostics, but > for long term reporting. People using DPDK-base

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Van Haaren, Harry
5 PM > To: Tom Crugnale; Stephen Hemminger > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v3 00/11] Port XStats > Ultimately the issue we are trying to solve is that there is no device > independent way to get any detailed statistics from NICs controlled by > DPDK. These stati

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Kyle Larose
On Thu, Oct 29, 2015 at 10:01 AM, Thomas Monjalon wrote: > So what is missing currently? Just having a consistent naming of > similar counters? A consistent naming scheme would certainly solve the problem. Thanks again, Kyle

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Kyle Larose
On Thu, Oct 29, 2015 at 9:10 AM, Thomas Monjalon wrote: > I don't understand. > The basic statistics are provided in a common API. > The other ones are not available in every NICs and can only be interpreted > while knowing the device. So what is the need exactly? The need is to provide informat

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Kyle Larose
: Wednesday, October 28, 2015 5:32 PM > To: Tom Crugnale > Cc: Harry van Haaren; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH v3 00/11] Port XStats > > On Wed, 28 Oct 2015 17:35:09 + > Tom Crugnale wrote: > >> Hi Harry, >> >> We are planning on

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Stephen Hemminger
On Wed, 28 Oct 2015 17:35:09 + Tom Crugnale wrote: > Hi Harry, > > We are planning on using the xstats API for periodic stats collection through > a polling thread. This would be done in a generic NIC agnostic manner, which > would require that the xstats identifiers have consistent namin

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-29 Thread Tom Crugnale
: Tom Crugnale Cc: Harry van Haaren; dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH v3 00/11] Port XStats On Wed, 28 Oct 2015 17:35:09 + Tom Crugnale wrote: > Hi Harry, > > We are planning on using the xstats API for periodic stats collection through > a polling thread. This w

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-28 Thread Tom Crugnale
[mailto:dev-boun...@dpdk.org] On Behalf Of Harry van Haaren Sent: Thursday, October 22, 2015 11:48 AM To: dev at dpdk.org Subject: [dpdk-dev] [PATCH v3 00/11] Port XStats This patchset adds an implementation of the xstats_get() and xstats_reset() API to the following PMDs: virtio, igb, igbvf, ixgbe, ixgbevf

[dpdk-dev] [PATCH v3 00/11] Port XStats

2015-10-22 Thread Harry van Haaren
This patchset adds an implementation of the xstats_get() and xstats_reset() API to the following PMDs: virtio, igb, igbvf, ixgbe, ixgbevf, i40e, i40evf and fm10k. The xstats API allows DPDK apps to gain access to extended statistics from each port on a NIC. These statistics are structured as per a