From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: About Throughput in BATMAN_V
Date: Mon, 08 Apr 2024 10:28:57 +0200 [thread overview]
Message-ID: <2066205.UkFFEUeh36@rousseau> (raw)
In-Reply-To: <171230441622.1066.17238774576163032219@diktynna.open-mesh.org>
On Friday, 5 April 2024 10:06:56 CEST berkay.demirci@protonmail.com wrote:
> We also did tests in virtual environment and according to this commit
> https://git.open-mesh.org/batman-adv.git/commit/6e860b3d5e4147bafcda32bf9b3
> e769926f232c5, ethtool link speed detection used to be disabled for such
> cases but got reverted since automatic measurements aren't implemented.
No. Batman-adv used the ethtool 'auto-negotiation' on/off state to decide
whether the the ethtool throughput value should be trusted.
As the commit states, the 'auto-negotiation' state has no impact on whether
the reported throughput value should be trusted. Auto-negotiation could be on
or off and still the value is wrong.
> dynamically calculating throughput is a must because like I said, one of our
> modems have a shorter distance range so it is faster when two nodes are
> close but as nodes move away, there is lots of packet loss so the real
> throughput drops as well, but with overriden throughput value stays the
> same.
You keep keep mentioning "modems have distance", "move away", "ethtool", etc
without having explained what your setup is. Without providing details about
these "modems with range" and what interface types you are talking about,
nobody can really comment on your setup.
> I see that the last patch for tp fallback was written in 2018, has there
> been no more progress since then? And what are the problems with it?
The main obstacle is time & energy to work on the tp fallback integration.
Open issues were mentioned in the responses to the various patches.
f you are interested n spending time on these patches, I am happy to provide
assistance.
Cheers,
Marek
next prev parent reply other threads:[~2024-04-08 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:56 About Throughput in BATMAN_V berkay.demirci
2024-04-03 13:16 ` Marek Lindner
2024-04-04 7:00 ` berkay.demirci
2024-04-04 10:00 ` Marek Lindner
2024-04-05 8:06 ` berkay.demirci
2024-04-08 8:28 ` Marek Lindner [this message]
2024-04-15 8:20 ` Berkay Demirci
2024-04-15 9:13 ` Marek Lindner
2024-04-15 18:27 ` Berkay Demirci
2024-05-19 14:33 ` Marek Lindner
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=2066205.UkFFEUeh36@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).