From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Lunn <andrew@lunn.ch>
Subject: Re: [RFC PATCH iproute2-next] System specification health API
Date: Sun, 16 Sep 2018 21:57:27 +0200
Message-ID: <20180916195727.GD19261@lunn.ch>
References: <1536826696-9413-1-git-send-email-eranbe@mellanox.com>
 <20180913103604.0ef868f4@cakuba.netronome.com>
 <20180916122939.498f7e0f@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
        Eran Ben Elisha <eranbe@mellanox.com>,
        netdev@vger.kernel.org, Jiri Pirko <jiri@mellanox.com>,
        Andy Gospodarek <andrew.gospodarek@broadcom.com>,
        Michael Chan <michael.chan@broadcom.com>,
        Simon Horman <simon.horman@netronome.com>,
        Alexander Duyck <alexander.duyck@gmail.com>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Tal Alon <talal@mellanox.com>,
        Ariel Almog <ariela@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from vps0.lunn.ch ([185.16.172.187]:35807 "EHLO vps0.lunn.ch"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1728460AbeIQBVd (ORCPT <rfc822;netdev@vger.kernel.org>);
        Sun, 16 Sep 2018 21:21:33 -0400
Content-Disposition: inline
In-Reply-To: <20180916122939.498f7e0f@xeon-e3>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

> Why is this going under iproute rather than using one of the existing sensor API's.
> For example Intel NIC's have thermal sensors etc.

Hi Stephen

These are not that sort of sensors. This is part of the naming problem
here. It is not really to do with health, it is about exceptions and
bugs. And the sensors are more like timeouts and watchdogs.

It is clear that the current names lead to a lot of confusion. Maybe:

health -> exception
sensor -> condition

       Andrew