All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Amit Cohen <amitc@mellanox.com>
Cc: mlxsw <mlxsw@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"o.rempel@pengutronix.de" <o.rempel@pengutronix.de>
Subject: Re: Link down reasons
Date: Wed, 27 May 2020 23:38:43 +0200	[thread overview]
Message-ID: <20200527213843.GC818296@lunn.ch> (raw)
In-Reply-To: <AM0PR0502MB38261D4F4F7A3BB5E0FDCD10D7B10@AM0PR0502MB3826.eurprd05.prod.outlook.com>

On Wed, May 27, 2020 at 03:41:22PM +0000, Amit Cohen wrote:
> Hi Andrew,
> 
> We are planning to send a set that exposes link-down reason in ethtool.
> 
> It seems that the ability of your set “Ethernet cable test support” can be
> integrated with link-down reason.
> 
>  
> 
> The idea is to expose reason and subreason (if there is):
> 
> $ ethtool ethX
> 
> …
> 
> Link detected: no (No cable) // No sub reason
> 
>  
> 
> $ ethtool ethY
> 
> Link detected: no (Autoneg failure, No partner detected)
> 
>  
> 
> Currently we have reason “cable issue” and subreasons “unsupported cable” and
> “shorted cable”.
> 
> The mechanism of cable test can be integrated and allow us report “cable issue”
> reason and “shorted cable” subreason.

Hi Amit

I don't really see them being combinable. First off, your API seems
too limiting. How do you say which pair is broken, or at what
distance? What about open cable, as opposed to shorted cable?

So i would suggest:

Link detected: no (cable issue)

And then recommend the user uses ethtool --cable-test to get all the
details, and you have a much more flexible API to provide as much or
as little information as you have.

   Andrew

       reply	other threads:[~2020-05-27 21:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM0PR0502MB38261D4F4F7A3BB5E0FDCD10D7B10@AM0PR0502MB3826.eurprd05.prod.outlook.com>
2020-05-27 21:38 ` Andrew Lunn [this message]
2020-05-28  5:56   ` Link down reasons Amit Cohen
2020-05-28  9:12     ` Petr Machata
2020-05-28 15:40       ` Andrew Lunn
2020-05-28 16:54         ` Petr Machata
2020-05-28 17:17           ` Michal Kubecek
2020-05-28 18:37           ` Andrew Lunn
2020-05-29  9:03             ` Petr Machata
2020-05-28  8:40 ` Oleksij Rempel
2020-05-28  9:22   ` Petr Machata
2020-05-28 10:28     ` Oleksij Rempel

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=20200527213843.GC818296@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=amitc@mellanox.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.