From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "Dave Täht" <dave.taht@gmail.com>,
Rpm <rpm@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
"Keith Winstein" <keithw@cs.stanford.edu>
Subject: Re: [Rpm] [Make-wifi-fast] tack - reducing acks on wlans
Date: Wed, 20 Oct 2021 22:37:37 +0200 [thread overview]
Message-ID: <FB3EEB77-C3A6-4752-931F-3239256B388A@gmx.de> (raw)
In-Reply-To: <878ryngbbe.fsf@toke.dk>
Hi Toke,
> On Oct 20, 2021, at 13:55, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Sebastian Moeller <moeller0@gmx.de> writes:
>
>> Just reading the introduction:
>> "It is well-studied that medium acquisition overhead in WLAN based on
>> the IEEE 802.11 medium access control (MAC) protocol [11] can severely
>> hamper TCP throughput, and TCP’s many small ACKs are one reason [53,
>> 69]. Basically, TCP sends an ACK for every one or two packets (i.e.,
>> received-packet-driven) [7, 15]. ACKs share the same medium route with
>> data packets, causing similar medium access overhead despite the much
>> smaller size of the ACK- s [8, 31, 36, 50, 58]. Contentions and
>> collisions, as well as the wasted wireless resources by ACKs, lead to
>> significant throughput decline on the data path (see §3.2)."
>>
>> makes me wonder whether the proper solution would not be to exchange
>> the WiFi MAC with something that is actually suited for existing
>> traffic patterns....
>
> Well, there are people who want to do that (replace the MAC); it's
> called LTE-U: https://en.wikipedia.org/wiki/LTE_in_unlicensed_spectrum
And here I thought their idea was to simply grab the "free" Frequency band and use them for their paid services....
> I'd much rather keep the WiFi MAC, thankyouverymuch. It may suck (for
> certain values of "suck"), but at least it doesn't impose a centralised
> controller on you :)
Well, if the price for a more effficient MAC is a central controller, I guess trying to patch up the symptoms of the current MAC is a much better strategy than I gave credit for.... ;)
Regards
Sebastian
>
> -Toke
prev parent reply other threads:[~2021-10-20 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 20:12 [Rpm] " Dave Taht
2021-10-19 20:25 ` Matt Mathis
2021-10-19 20:31 ` Omer Shapira
2021-10-20 7:00 ` [Rpm] [Make-wifi-fast] " Michael Welzl
2021-10-20 9:44 ` Toke Høiland-Jørgensen
2021-10-20 10:13 ` Michael Welzl
2021-10-20 10:44 ` Toke Høiland-Jørgensen
2021-10-20 10:54 ` Michael Welzl
2021-10-20 11:52 ` Toke Høiland-Jørgensen
2021-10-20 12:21 ` Michael Welzl
2021-10-20 15:57 ` Toke Høiland-Jørgensen
2021-10-20 17:08 ` Michael Welzl
2021-10-20 22:04 ` Toke Høiland-Jørgensen
2021-10-20 23:06 ` Anna Brunström
2021-10-21 6:01 ` Michael Welzl
2021-10-20 23:20 ` Omer Shapira
2021-10-21 6:19 ` Michael Welzl
2021-10-21 7:18 ` Michael Welzl
2021-10-21 7:57 ` Keith Winstein
2021-10-21 8:42 ` Michael Welzl
2021-10-21 20:19 ` Keith Winstein
2021-10-20 23:08 ` Omer Shapira
2021-10-20 10:58 ` [Rpm] " Sebastian Moeller
2021-10-20 11:55 ` [Rpm] [Make-wifi-fast] " Toke Høiland-Jørgensen
2021-10-20 20:37 ` Sebastian Moeller [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FB3EEB77-C3A6-4752-931F-3239256B388A@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@gmail.com \
--cc=keithw@cs.stanford.edu \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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