b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 04 Apr 2024 12:00:22 +0200	[thread overview]
Message-ID: <3327582.AxlXzFCzgd@rousseau> (raw)
In-Reply-To: <171221400877.1066.8144265750602425260@diktynna.open-mesh.org>

Hi,

> We have two modems for each node and in one of them, expected throughput
> should be about 6 Mb/s for example, and in the other one it should be about
> 30 Mb/s. By using iperf and also throughput meter I can see that it's the
> case. But when they are added to batman with batctl if add, after typing
> batctl o, I see that the throughput values in both interfaces are 10000
> instead.
> 
> I looked at the interfaces with ethtool and the speed is 10000 Mb/s there
> for both too which is how batman must be measuring the throughput

correct. If the underlying interface provides a link speed via ethtool, batman 
uses the ethtool API to get the throughput value.


> If we use throughput override, it's fine at first but one of the modems has a
> shorter range so in our test where two nodes move away from each other,
> actual throughput gets decreased due to losses but batman still chooses the
> same interface due to the overriden value.

That is what the manual override is meant to do. A manual value that will 
override all dynamically determined values.

Can you explain what type if "modem" you are talking about? It is not clear 
why a modem depends on range. Or are you talking about a batman mesh 
connecting various modems? Please share the topology of your setup.

Is this somehow related to your earlier statement: "[..] but then even when 
actual throughput of the active interface decreases, it doesn't switch to the 
other interface because it only considers the overriden value." ?


> Basically I would prefer batman being able to change measured throughput
> dynamically.

if I understand correctly you are changing from "Batman doesn't seem to 
calculate throughput properly" to "measured throughput is preferable" ? There 
is no calculation issue with batman v?

Cheers,
Marek




  reply	other threads:[~2024-04-04 10:00 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 [this message]
2024-04-05  8:06       ` berkay.demirci
2024-04-08  8:28         ` Marek Lindner
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=3327582.AxlXzFCzgd@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).