From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Remi Pommarel <repk@triplefau.lt>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH RFC 2/2] batman-adv: Better half duplex penalty estimation
Date: Sat, 14 Oct 2023 08:03:47 +0200 [thread overview]
Message-ID: <ZSonvL2bJUx3qyBO@sellars> (raw)
In-Reply-To: <ZSoixFsJi5vYCRxh@sellars>
On Sat, Oct 14, 2023 at 07:10:28AM +0200, Linus Lüssing wrote:
> In the following scenario:
>
> +-------+ ch.1 +-------+ ch.2 +-------+ ch.2 +-------+
> | Orig0 | <----- | Orig1 | <------ | Orig2 | <------ | Orig3 |
> +-------+ 300 +-------+ 30000 +-------+ 110 +-------+
> ^ |
> | ch.3 |
> +-----------------------------------+
> 100
>
> Would the results on Orig2 to Orig1 be these?
Sorry, I ment "on Orig3 to Orig0" here.
> - via Orig2: 300*110 / (300+110) = 80.5
> - via Orig1: 100 <- selected
>
> While it should have been this?
> - via Orig2: 30000*110 / (30000+110) = 109.6 <- selected
> - via Orig1: 100
next prev parent reply other threads:[~2023-10-14 6:04 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 [this message]
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
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=ZSonvL2bJUx3qyBO@sellars \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=repk@triplefau.lt \
/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 NNTP newsgroup(s).