From: Stephen Hemminger <stephen@networkplumber.org>
To: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Cc: dev@dpdk.org, reshma.pattan@intel.com, deepak.k.jain@intel.com,
harry.van.haaren@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/3] drivers/net: add support for IF-MIB and EtherLike-MIB
Date: Mon, 22 May 2017 09:11:00 -0700 [thread overview]
Message-ID: <20170522091100.27f080e3@xeon-e3> (raw)
In-Reply-To: <20170522143202.22424-1-michalx.k.jastrzebski@intel.com>
On Mon, 22 May 2017 16:31:59 +0200
Michal Jastrzebski <michalx.k.jastrzebski@intel.com> wrote:
> Extend Intel NICs (i40e, ixgbe, e1000) xstats for IF-MIB and
> EtherLike-MIB.
>
> If-MIB xstats:
> ifNumber
> ifIndex
> ifType
> ifMtu
> ifSpeed
> ifPhysAddress
> ifOperStatus
> ifLastChange
> ifHighSpeed
> ifConnectorPresent
> ifCounterDiscontinuityTime
>
> EtherLike-MIB xstats:
> dot3PauseOperMode
> dot3StatsDuplexStatus
> dot3StatsRateControlAbility
> dot3StatsRateControlStatus
> dot3ControlFunctionsSupported
>
> Michal Jastrzebski (3):
> drivers/net: add support for IF-MIB and EtherLike-MIB for e1000
> drivers/net: add support for IF-MIB and EtherLike-MIB for i40e
> drivers/net: add support for IF-MIB and EtherLike-MIB for ixgbe
>
> drivers/net/e1000/e1000_ethdev.h | 59 ++++++++
> drivers/net/e1000/igb_ethdev.c | 296 ++++++++++++++++++++++++++++++++++----
> drivers/net/i40e/i40e_ethdev.c | 171 +++++++++++++++++++++-
> drivers/net/i40e/i40e_ethdev.h | 60 ++++++++
> drivers/net/ixgbe/ixgbe_ethdev.c | 275 ++++++++++++++++++++++++++++++++---
> drivers/net/ixgbe/ixgbe_ethdev.h | 59 ++++++++
> 6 files changed, 878 insertions(+), 42 deletions(-)
>
Having all the SNMP MIB information is a worth goal. Thank you for starting
the effort.
But you need to rethink how you are implementing this.
Doing it in a driver specific manner is not helpful to application writers.
All API's for features like this should be at ethdev level, and be supported
by generic code.
If you are going to add something like this it has to work for all devices
virtual, physical, layered and not just Intel hardware. It is a much
bigger task.
prev parent reply other threads:[~2017-05-22 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 14:31 Michal Jastrzebski
2017-05-22 14:32 ` [dpdk-dev] [PATCH 1/3] drivers/net: add support for IF-MIB and EtherLike-MIB for e1000 Michal Jastrzebski
2017-05-22 16:16 ` Pattan, Reshma
2017-05-22 16:34 ` Pattan, Reshma
2017-05-23 5:53 ` Lu, Wenzhuo
2017-06-20 11:38 ` Radu Nicolau
2017-06-26 9:42 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2017-06-27 11:08 ` Ferruh Yigit
2017-06-27 11:21 ` Bruce Richardson
2017-06-27 11:36 ` Ferruh Yigit
2017-07-05 13:02 ` Pattan, Reshma
2017-06-27 22:26 ` Stephen Hemminger
2017-07-06 11:48 ` Pattan, Reshma
2017-07-19 10:40 ` Ferruh Yigit
2017-05-22 14:32 ` [dpdk-dev] [PATCH 2/3] drivers/net: add support for IF-MIB and EtherLike-MIB for i40e Michal Jastrzebski
2017-05-31 5:29 ` Xing, Beilei
2017-06-26 9:41 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2017-05-22 14:32 ` [dpdk-dev] [PATCH 3/3] drivers/net: add support for IF-MIB and EtherLike-MIB for ixgbe Michal Jastrzebski
2017-06-26 9:39 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2017-06-27 22:27 ` Stephen Hemminger
2017-05-22 16:11 ` Stephen Hemminger [this message]
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=20170522091100.27f080e3@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=michalx.k.jastrzebski@intel.com \
--cc=reshma.pattan@intel.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).