From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Marek Lindner <marek.lindner@mailbox.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org,
"René Treffer" <treffer@measite.de>,
"Andrew Strohman" <andrew@andrewstrohman.com>
Subject: Re: [PATCH RFC] batman-adv: BATMAN V: use/prefer 11s airtime link metric
Date: Sun, 19 Jan 2025 06:15:50 +0100 [thread overview]
Message-ID: <Z4yKhoN0x_Ckdu-u@sellars> (raw)
In-Reply-To: <Z4yIKYsFvLyGpmjt@sellars>
On Sun, Jan 19, 2025 at 06:05:45AM +0100, Linus Lüssing wrote:
> On Sat, Jan 18, 2025 at 05:59:56AM +0100, Marek Lindner wrote:
> > FYI, expected throughput and also 802.11 throughput estimation are taking
> > congestion into account.
>
> Are they? At least in minstrel_ht_get_tp_avg() I don't see it:
On the other hand, if the channel were fully utilized then this
should likely, indirectly reduce the average transmission success probability
a bit. So in that case I guess congestion / channel utilization could
indirectly be factored in.
But still if a channel is 90% utilized / has 90% airtime usage then this
wouldn't mean that the expected throughput from Minstrel will be about
90% lower compared to an fully free channel, I guess?
next prev parent reply other threads:[~2025-01-19 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 0:35 [PATCH RFC] batman-adv: BATMAN V: use/prefer 11s airtime link metric Linus Lüssing
2025-01-18 2:00 ` Andrew Strohman
2025-01-18 4:59 ` Marek Lindner
2025-01-19 3:20 ` Andrew Strohman
2025-01-19 3:48 ` Marek Lindner
2025-01-19 4:28 ` Linus Lüssing
2025-01-19 5:05 ` Linus Lüssing
2025-01-19 5:15 ` Linus Lüssing [this message]
2025-01-18 5:08 ` 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=Z4yKhoN0x_Ckdu-u@sellars \
--to=linus.luessing@c0d3.blue \
--cc=andrew@andrewstrohman.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=marek.lindner@mailbox.org \
--cc=treffer@measite.de \
/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.