netdev - Re: ethtool TODO list

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]

Message-ID: <20160712191828.GB22464@tuxdriver.com>
Date:	Tue, 12 Jul 2016 15:18:28 -0400
From:	"John W. Linville" <linville@...driver.com>
To:	David Miller <davem@...emloft.net>
Cc:	jorge.garcia.gonzalez@...il.com, jiri@...nulli.us,
	ben@...adent.org.uk, netdev@...r.kernel.org
Subject: Re: ethtool TODO list - additional info

On Tue, Jul 12, 2016 at 11:34:06AM -0700, David Miller wrote:
> From: "John W. Linville" <linville@...driver.com>
> Date: Tue, 12 Jul 2016 14:12:52 -0400
> 
> > I haven't heard a strong case for why it is necessary.
> 
> Stats on large scale setups/systems is problematic and ethtool
> is a part of that problem.
> 
> Extensibility in general suffers because of the ioctl() interface as
> well.
> 
> For getting ethtool settings or stats, we have no clean filtering
> mechanism.
> 
> I could go on and on...
> 
> I think before any new features are added to ethtool, we move over to
> the netlink based interface and lock the existing ioctl() API in stone.

OK, then I'll start looking at this. Thanks for providing some clarity!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.