From: Remi Pommarel <repk@triplefau.lt>
To: Marek Lindner <mareklindner@neomailbox.ch>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH RFC 0/2] Better throughput estimation on half duplex interfaces
Date: Thu, 28 Sep 2023 19:54:38 +0200 [thread overview]
Message-ID: <ZRW93njVI0eRKI2O@pilgrim> (raw)
In-Reply-To: <ZRWuVBZuzD7cdd_-@pilgrim>
And of course I messed up both batctl o outputs.
On Thu, Sep 28, 2023 at 06:48:21PM +0200, Remi Pommarel wrote:
> On Thu, Sep 28, 2023 at 05:33:46PM +0200, Marek Lindner wrote:
> >
> > Maybe you can add throughput metric values to your example and then expand on
> > what you find problematic?
>
[ ... ]
>
> $ batctl o
> Originator last-seen ( throughput) Nexthop [outgoingIF]
> * Orig0-Main-Mac 0.220s ( 110) Orig1-mesh0-Mac [ mesh0 ]
> Orig0-Main-Mac 0.220s ( 100) Orig1-mesh0-Mac [ mesh0 ]
Is in fact
$ batctl o
Originator last-seen ( throughput) Nexthop [outgoingIF]
* Orig0-Main-Mac 0.220s ( 110) Orig1-mesh0-Mac [ mesh0 ]
Orig0-Main-Mac 0.220s ( 100) Orig0-mesh0-Mac [ mesh0 ]
(The last line nexthop was wrong)
and
>
> So best path for Orig2 to Orig0 would go through Orig1 with an expected
> throughput of 110Mbps. But such a throughput cannot be reached because
> Orig1 has to forward packet from and to the same WiFi interface.
>
> If the throughput between Orig1 and Orig2 were to be 160Mbps instead of
> previous 110Mbps then the originator table on Orig2 will look like that:
>
> $ batctl o
> Originator last-seen ( throughput) Nexthop [outgoingIF]
> Orig0-Main-Mac 0.220s ( 80) Orig1-mesh0-Mac [ mesh0 ]
> * Orig0-Main-Mac 0.220s ( 100) Orig1-mesh0-Mac [ mesh0 ]
>
Is in fact
$ batctl o
Originator last-seen ( throughput) Nexthop [outgoingIF]
* Orig0-Main-Mac 0.220s ( 80) Orig1-mesh0-Mac [ mesh0 ]
Orig0-Main-Mac 0.220s ( 100) Orig0-mesh0-Mac [ mesh0 ]
(Same error here)
Sorry about that,
--
Remi
next prev parent reply other threads:[~2023-09-28 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 12:39 [PATCH RFC 0/2] Better throughput estimation on half duplex interfaces Remi Pommarel
2023-09-28 12:39 ` [PATCH RFC 1/2] batman-adv: Keep half duplex penalty on OGM receiving side also Remi Pommarel
2023-09-28 12:39 ` [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation Remi Pommarel
2023-10-14 5:10 ` Linus Lüssing
2023-10-14 6:03 ` Linus Lüssing
2023-10-18 19:58 ` Remi Pommarel
2023-10-18 21:37 ` Nicolas Escande
2023-10-14 6:24 ` Linus Lüssing
2023-09-28 15:33 ` [PATCH RFC 0/2] Better throughput estimation on half duplex interfaces Marek Lindner
2023-09-28 16:48 ` Remi Pommarel
2023-09-28 17:54 ` Remi Pommarel [this message]
2023-09-28 18:10 ` Marek Lindner
2023-09-28 19:16 ` Remi Pommarel
2023-10-03 21:06 ` Marek Lindner
2023-10-11 8:55 ` Remi Pommarel
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=ZRW93njVI0eRKI2O@pilgrim \
--to=repk@triplefau.lt \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
/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.