DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/7] ether: don't mark input multicast for deprecation
Date: Thu, 12 Nov 2015 17:52:24 +0100	[thread overview]
Message-ID: <2206525.9MQsTNsirq@xps13> (raw)
In-Reply-To: <1446771879-3979-2-git-send-email-stephen@networkplumber.org>

2015-11-05 17:04, Stephen Hemminger:
> The number of received multicast frames is useful and already
> available in many/most drivers. Therefore don't mark it as
> deprecated.

There are other useful stats in xstats.
The idea of this basic stats structure is to provide only
the really mandatory and basic counters.
A multicast counter is not so basic and won't be implemented everywhere.

This patch won't be applied.
We'll need a consensus to definitively remove the deprecated stats.

  reply	other threads:[~2015-11-12 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  1:04 [dpdk-dev] [PATCH v2 0/7] ethdev: force deprecation of statistics Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 1/7] ether: don't mark input multicast for deprecation Stephen Hemminger
2015-11-12 16:52   ` Thomas Monjalon [this message]
2015-11-12 22:10   ` Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 2/7] bond: don't sum deprecated statistics Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 3/7] cxgbe: don't report " Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 4/7] i40e: " Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 5/7] e1000: " Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 6/7] test-pmd: remove references to " Stephen Hemminger
2015-11-06  1:04 ` [dpdk-dev] [PATCH 7/7] rte_ether: mark deprecated statistics with attribute Stephen Hemminger
2015-11-12 22:03   ` Thomas Monjalon
2015-11-12 22:07 ` [dpdk-dev] [PATCH v2 0/7] ethdev: force deprecation of statistics 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=2206525.9MQsTNsirq@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --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).