On Tue, Jul 12, 2016 at 11:34:06AM -0700, David Miller wrote:
> From: "John W. Linville"
> 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
From: "John W. Linville"
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()
On 16-07-12 11:12 AM, John W. Linville wrote:
> On Tue, Jul 12, 2016 at 01:04:52PM -0500, Jorge Alberto Garcia wrote:
>> On Tue, Jul 12, 2016 at 12:55 PM, Jiri Pirko wrote:
>>> Tue, Jul 05, 2016 at 05:37:42PM CEST, jorge.garcia.gonza...@gmail.com wrote:
Hi !
Some
On Tue, Jul 12, 2016 at 01:04:52PM -0500, Jorge Alberto Garcia wrote:
> On Tue, Jul 12, 2016 at 12:55 PM, Jiri Pirko wrote:
> > Tue, Jul 05, 2016 at 05:37:42PM CEST, jorge.garcia.gonza...@gmail.com wrote:
> >>Hi !
> >>
> >>Some days ago, Jiri Pirko was talking about some next
On Tue, Jul 12, 2016 at 12:55 PM, Jiri Pirko wrote:
> Tue, Jul 05, 2016 at 05:37:42PM CEST, jorge.garcia.gonza...@gmail.com wrote:
>>Hi !
>>
>>Some days ago, Jiri Pirko was talking about some next steps to
>>implement for ethtool.
>>
>> I haven't seen any follow up since
Tue, Jul 05, 2016 at 05:37:42PM CEST, jorge.garcia.gonza...@gmail.com wrote:
>Hi !
>
>Some days ago, Jiri Pirko was talking about some next steps to
>implement for ethtool.
>
> I haven't seen any follow up since ethtool's maintainer change. Can we have
>additional details about these ?
>
>-
Hi !
Some days ago, Jiri Pirko was talking about some next steps to
implement for ethtool.
I haven't seen any follow up since ethtool's maintainer change. Can we have
additional details about these ?
- libethtool - API
- generic netlink
- sub commands syntax
- TODO/bugzilla
On Mon, Jul 4,