From: David Miller <davem@davemloft.net>
To: mark.d.rustad@intel.com
Cc: bhutchings@solarflare.com, florian@openwrt.org,
jeffrey.t.kirsher@intel.com, donald.c.skidmore@intel.com,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next 3/3] ixgbe: add syfs interface for to export read only driver information
Date: Thu, 05 Apr 2012 20:59:42 -0400 (EDT) [thread overview]
Message-ID: <20120405.205942.91469949871612514.davem@davemloft.net> (raw)
In-Reply-To: <81212BCD-D022-4B71-955A-96B6C8E2A5DC@intel.com>
From: "Rustad, Mark D" <mark.d.rustad@intel.com>
Date: Thu, 5 Apr 2012 23:52:40 +0000
> The redundancy with ethtool doesn't bother me much, because I think
> sysfs is a more general way to export driver information, and I find
> it very convenient to get as much as is practical from a single
> source. I really like doing "grep . * */*" in sysfs and getting as
> much information as possible about a driver.
That's not our position, we have flexible, extensible, interfaces
such as ethtool and netlink so that people don't get the urge
to toss random unnecessary junk into sysfs.
There are no damn APIs for what driver guys want to put into
sysfs, making it terrible from a user's perspective.
Whereas ethtool and netlink give you something consistent and
reliable.
Therefore there will be hard pushback on anything one tries to
export via sysfs, it is almost guarenteed that ethtool and
netlink fit the bill properly.
prev parent reply other threads:[~2012-04-06 0:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 10:47 [net-next 0/3][pull request] Intel Wired LAN Driver Update Jeff Kirsher
2012-04-05 10:47 ` [net-next 1/3] ixgbe: add support functions to access thermal data Jeff Kirsher
2012-04-05 10:47 ` [net-next 2/3] ixgbe: add hwmon interface to export " Jeff Kirsher
2012-04-05 10:47 ` [net-next 3/3] ixgbe: add syfs interface for to export read only driver information Jeff Kirsher
2012-04-05 12:19 ` Florian Fainelli
2012-04-05 16:32 ` Ben Hutchings
2012-04-05 22:49 ` David Miller
2012-04-05 23:01 ` Skidmore, Donald C
2012-04-05 23:52 ` Rustad, Mark D
2012-04-06 0:59 ` David Miller [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=20120405.205942.91469949871612514.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=donald.c.skidmore@intel.com \
--cc=florian@openwrt.org \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mark.d.rustad@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).