public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH] batman-adv: Revert "disable ethtool link speed detection when auto negotiation off"
Date: Mon, 25 Nov 2019 18:02:17 +0800	[thread overview]
Message-ID: <21004470.HqcN17L5CA@rousseau> (raw)
In-Reply-To: <20191125094650.12435-1-sven@narfation.org>

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

On Monday, 25 November 2019 17:46:50 HKT Sven Eckelmann wrote:
> The commit d60b8fc69ef2 ("batman-adv: disable ethtool link speed detection
> when auto negotiation off") disabled the usage of ethtool's link_ksetting
> when auto negotation was enabled due to invalid values when used with
> tun/tap virtual net_devices. According to the patch, automatic measurements
> should be used for these kind of interfaces.
> 
> But there are major flaws with this argumentation:
> 
> * automatic measurements are not implemented
> * auto negotiation has nothing to do with the validity of the retrieved
>   values
> 
> The first point has to be fixed by a longer patch series. The "validity"
> part of the second point must be addressed in the same patch series by
> dropping the usage of ethtool's link_ksetting (thus always doing automatic
> measurements over ethernet).
> 
> Drop the patch again to have more default values for various net_device
> types/configurations. The user can still overwrite them using the
> batadv_hardif's BATADV_ATTR_THROUGHPUT_OVERRIDE.

I am not quite clear on how reverting this patch will get us better default 
values. In the case reported by Matthias the autoneg detection was working as 
intended by this very patch you are reverting. As Antonio had originally 
outlined:

The problem with autonegotiation disabled is that the advertised speed
is likely to be a random number set by default by the driver.

This patch was the main reason why Matthias (or Gluon users) even realized 
that there was an issue with certain Ethernet ports & BATMAN V. Without the 
patch BATMAN V may have created routing loops and Gluon users would complain 
about those instead.

There is no disagreement that the situation needs improving but why is 
reverting this autoneg patch the best course of action ?

Cheers,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-25 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25  9:46 [PATCH] batman-adv: Revert "disable ethtool link speed detection when auto negotiation off" Sven Eckelmann
2019-11-25 10:02 ` Marek Lindner [this message]
2019-11-25 10:25   ` Sven Eckelmann

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=21004470.HqcN17L5CA@rousseau \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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