From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gal Pressman Subject: Re: [RFC PATCH net-next 0/3] ethtool: Add link down reason reporting Date: Thu, 22 Jun 2017 14:13:41 +0300 Message-ID: References: <1498050286-17141-1-git-send-email-galp@mellanox.com> <20170621084415.4a4b54ac@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, "David S. Miller" , "John W. Linville" , Saeed Mahameed , Vidya Sagar Ravipati , Jiri Pirko , David Decotigny , kernel-team@fb.com To: Stephen Hemminger Return-path: Received: from mail-ve1eur01on0061.outbound.protection.outlook.com ([104.47.1.61]:62784 "EHLO EUR01-VE1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752918AbdFVLNu (ORCPT ); Thu, 22 Jun 2017 07:13:50 -0400 In-Reply-To: <20170621084415.4a4b54ac@xeon-e3> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: > 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.