[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c30eb6ba-dd73-1bd9-9ceb-40fe2f9e0408@mellanox.com>
Date: Thu, 22 Jun 2017 14:13:41 +0300
From: Gal Pressman <galp@...lanox.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
"John W. Linville" <linville@...driver.com>,
Saeed Mahameed <saeedm@...lanox.com>,
Vidya Sagar Ravipati <vidya@...ulusnetworks.com>,
Jiri Pirko <jiri@...lanox.com>,
David Decotigny <decot@...glers.com>, kernel-team@...com
Subject: Re: [RFC PATCH net-next 0/3] ethtool: Add link down reason reporting
> Ethtool doesn't work well as a monitoring/event interface.
> Maybe this would be better as extended information with the netlink UP/DOW event.
This API is not meant for monitoring events.
The main use case here is a new interface that's down and won't go up for some reason.
Nothing will magically change until someone fixes the issue, logging the reason as an event on
netdev creation seems less convenient to me.
Powered by blists - more mailing lists