From: "John W. Linville" <linville@tuxdriver•com>
To: David Miller <davem@davemloft•net>
Cc: jorge.garcia.gonzalez@gmail•com, jiri@resnulli•us,
ben@decadent•org.uk, netdev@vger•kernel.org
Subject: Re: ethtool TODO list - additional info
Date: Tue, 12 Jul 2016 15:18:28 -0400 [thread overview]
Message-ID: <20160712191828.GB22464@tuxdriver.com> (raw)
In-Reply-To: <20160712.113406.1402587122290887574.davem@davemloft.net>
On Tue, Jul 12, 2016 at 11:34:06AM -0700, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver•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@tuxdriver•com might be all we have. Be ready.
prev parent reply other threads:[~2016-07-12 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 15:37 ethtool TODO list - additional info Jorge Alberto Garcia
2016-07-12 17:55 ` Jiri Pirko
2016-07-12 18:04 ` Jorge Alberto Garcia
2016-07-12 18:12 ` John W. Linville
2016-07-12 18:25 ` John Fastabend
2016-07-12 18:34 ` David Miller
2016-07-12 19:18 ` John W. Linville [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=20160712191828.GB22464@tuxdriver.com \
--to=linville@tuxdriver$(echo .)com \
--cc=ben@decadent$(echo .)org.uk \
--cc=davem@davemloft$(echo .)net \
--cc=jiri@resnulli$(echo .)us \
--cc=jorge.garcia.gonzalez@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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