From: Andrew Lunn <andrew@lunn.ch>
To: Stephen Hemminger <stephen@networkplumber.org>
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>
Subject: Re: [RFC PATCH iproute2-next] System specification health API
Date: Sun, 16 Sep 2018 21:57:27 +0200 [thread overview]
Message-ID: <20180916195727.GD19261@lunn.ch> (raw)
In-Reply-To: <20180916122939.498f7e0f@xeon-e3>
> 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
next prev parent reply other threads:[~2018-09-17 1:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 8:18 [RFC PATCH iproute2-next] System specification health API Eran Ben Elisha
2018-09-13 8:18 ` [RFC PATCH iproute2-next] man: Add devlink health man page Eran Ben Elisha
2018-09-13 10:27 ` Tobin C. Harding
2018-09-13 11:58 ` Eran Ben Elisha
2018-09-13 22:06 ` Tobin C. Harding
2018-09-13 12:08 ` Andrew Lunn
2018-09-13 12:49 ` Eran Ben Elisha
2018-09-13 13:24 ` Andrew Lunn
2018-09-13 14:30 ` Eran Ben Elisha
2018-09-13 15:12 ` Andrew Lunn
2018-09-16 9:14 ` Eran Ben Elisha
2018-09-13 17:36 ` [RFC PATCH iproute2-next] System specification health API Jakub Kicinski
2018-09-16 10:37 ` Eran Ben Elisha
2018-09-25 12:00 ` Eran Ben Elisha
2018-09-16 19:29 ` Stephen Hemminger
2018-09-16 19:57 ` Andrew Lunn [this message]
2018-09-25 12:17 ` Eran Ben Elisha
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=20180916195727.GD19261@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexander.duyck@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=ariela@mellanox.com \
--cc=eranbe@mellanox.com \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=stephen@networkplumber.org \
--cc=talal@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).