All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	David Marchand <david.marchand@redhat.com>,
	arybchenko@solarflare.com, "Stokes, Ian" <ian.stokes@intel.com>
Subject: Re: [dpdk-dev] [RFC PATCH 1/2] ethdev: introduce internal rxq/txq stats API
Date: Fri, 12 Apr 2019 15:18:46 +0200	[thread overview]
Message-ID: <5210965.CNSgfQvn2d@xps> (raw)
In-Reply-To: <20190319105401.0974a7ac@shemminger-XPS-13-9360>

19/03/2019 18:54, Stephen Hemminger:
> My preference would be:
>   1. Make all DPDK drivers consistent in usage of current statistic values.
>   2. Propose an enhancement to have new ethdev statistics match some pre-existing
>      standard like SNMP or other RFC.

This patch is about basic stats.
What would be different if looking at SNMP or other?

>   3. Reduce custom (xstats) values by using #2. Leave it for driver specific stuff.
> 
> I.e: don't modify existing API at all, make a new one.

This patch does not modify the API.




  reply	other threads:[~2019-04-12 13:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 11:18 [PATCH 00/12] rxq q_errors[] statistics fixes David Marchand
2019-03-04 11:18 ` [PATCH 01/12] net/af_packet: fix incorrect rxq errors stat David Marchand
2019-03-04 11:18 ` [PATCH 02/12] net/avp: " David Marchand
2019-03-04 12:18   ` Legacy, Allain
2019-03-04 11:18 ` [PATCH 03/12] net/bnxt: " David Marchand
2019-03-04 11:18 ` [PATCH 04/12] net/cxgbe: " David Marchand
2019-03-04 11:18 ` [PATCH 05/12] net/kni: " David Marchand
2019-03-04 11:18 ` [PATCH 06/12] net/mlx4: " David Marchand
2019-03-05  8:19   ` Shahaf Shuler
2019-03-04 11:18 ` [PATCH 07/12] net/mlx5: " David Marchand
2019-03-05  8:18   ` Shahaf Shuler
2019-03-04 11:18 ` [PATCH 08/12] net/null: " David Marchand
2019-03-04 11:18 ` [PATCH 09/12] net/pcap: " David Marchand
2019-03-04 11:18 ` [PATCH 10/12] net/ring: " David Marchand
2019-03-04 11:18 ` [PATCH 11/12] net/szedata2: " David Marchand
2019-03-04 11:18 ` [PATCH 12/12] net/tap: " David Marchand
2019-03-04 13:58   ` Wiles, Keith
2019-03-11 17:22 ` [PATCH 00/12] rxq q_errors[] statistics fixes Ferruh Yigit
2019-03-11 18:09   ` David Marchand
2019-03-14 15:12     ` David Marchand
2019-03-14 15:13       ` [RFC PATCH 1/2] ethdev: introduce internal rxq/txq stats API David Marchand
2019-03-14 15:13         ` [RFC PATCH 2/2] net/af_packet: convert to new " David Marchand
2019-03-15 13:30         ` [RFC PATCH 1/2] ethdev: introduce internal " David Marchand
2019-03-19 17:18         ` Ferruh Yigit
2019-03-19 17:54           ` Stephen Hemminger
2019-04-12 13:18             ` Thomas Monjalon [this message]
2019-03-26  9:29           ` David Marchand
2019-04-12 13:29             ` [dpdk-dev] " Thomas Monjalon
2019-04-12 14:32               ` David Marchand
2019-04-12 16:05                 ` Stephen Hemminger
2019-04-12 15:07   ` [dpdk-dev] [PATCH 00/12] rxq q_errors[] statistics fixes Thomas Monjalon
2019-04-12 15:38     ` Ferruh Yigit
2019-04-12 15:45       ` Thomas Monjalon
2019-04-12 15:57         ` Ferruh Yigit
2019-05-28 21:38 ` Yigit, Ferruh

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=5210965.CNSgfQvn2d@xps \
    --to=thomas@monjalon.net \
    --cc=arybchenko@solarflare.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ian.stokes@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.