netdev - Re: [net-next 3/3] ixgbe: add syfs interface for to export read only driver information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 05 Apr 2012 20:59:42 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	mark.d.rustad@...el.com
Cc:	bhutchings@...arflare.com, florian@...nwrt.org,
	jeffrey.t.kirsher@...el.com, donald.c.skidmore@...el.com,
	netdev@...r.kernel.org, gospo@...hat.com, sassmann@...hat.com
Subject: Re: [net-next 3/3] ixgbe: add syfs interface for to export read
 only driver information

From: "Rustad, Mark D" <mark.d.rustad@...el.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.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html