From: Francois Romieu <romieu@fr.zoreil.com>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: Rajesh Borundia <rajesh.borundia@qlogic.com>,
Ethan Zhao <ethan.zhao@oracle.com>,
Manish Chopra <manish.chopra@qlogic.com>,
Sony Chacko <sony.chacko@qlogic.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] netxen: fix ethtool rx_dropped information in ethtool get_ethtool_stats()
Date: Sat, 19 Jul 2014 12:19:46 +0200 [thread overview]
Message-ID: <20140719101946.GA4319@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <049BCC6F-0A2E-421A-9873-0B7ED6FFB3AC@gmail.com>
Ethan Zhao <ethan.kernel@gmail.com> :
> ?? 2014??7??19????????2:21??Rajesh Borundia <rajesh.borundia@qlogic.com> ??????
[...]
> > I think ethtool stats are adapter specific. Driver does not maintain
> > rx_dropped stats and we also don't get it from adapter. I am not
> > sure if ethtool stats should match ifconfig stats as ifconfig also
> > adds net core stats to adapter stats.
> I held the same point as yours before I read more drivers implementation
> under Ethernet dir, in fact there is no specification/convention that
> ethtool info is adapter specific. All information output by ethtool is
> based on the information name itself, one fact we want this patch is
> netxen defined 'rx dropped' field but output nothing.
It may be fine as a requirement of the day but it does not bode well
for the future as ethtool stats API won't get less messy.
I'd rather see ethtool stats provides one of those:
1. hardware stats only
2. driver dependent stats - anything you want - as long as the hardware
only part of the stats is clearly identified
2. needs works. 1. hurts any requirement where it would priviously had
been so easy to add a few lines of code in the driver and push the mess
straight from kernel to the end user application.
--
Ueimor
next prev parent reply other threads:[~2014-07-19 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 3:43 Ethan Zhao
2014-07-18 3:47 ` Varka Bhadram
2014-07-18 6:05 ` Ethan Zhao
2014-07-18 6:08 ` Varka Bhadram
2014-07-18 18:21 ` Rajesh Borundia
2014-07-19 5:45 ` Ethan Zhao
2014-07-19 10:19 ` Francois Romieu [this message]
2014-07-19 11:45 ` Ethan Zhao
2014-07-19 16:28 ` Francois Romieu
2014-07-20 0:43 ` Ethan Zhao
2014-07-20 2:52 ` Ethan Zhao
2014-07-20 18:01 ` Francois Romieu
2014-07-21 1:56 ` Ethan Zhao
2014-07-21 3:58 ` David Miller
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=20140719101946.GA4319@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=ethan.kernel@gmail.com \
--cc=ethan.zhao@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.chopra@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.com \
--cc=sony.chacko@qlogic.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
all inboxes | Powered by JetHome®