From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
Keith Winstein <keithw@cs.stanford.edu>
Subject: Re: [Make-wifi-fast] [Rpm] tack - reducing acks on wlans
Date: Wed, 20 Oct 2021 12:58:11 +0200 [thread overview]
Message-ID: <D464EE6A-CB65-41F0-BA70-BCFE4DA4ECC1@gmx.de> (raw)
In-Reply-To: <CAA93jw6Ktn3r413QYt3rA+B5aYFy=Ph359LtOoPEo+9buCtdbw@mail.gmail.com>
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....
On the other hand the Reno-ACK scheme is probably not really optimal today (if it ever was in the past) so improving transport-level feed-back schemes seems a worthy goal in itself.
But really, a packet network should be able to simply transport all packets reasonably efficiently..., no?
Regards
Sebastian
> On Oct 19, 2021, at 22:12, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> Somehow I'd missed this paper... thx for the steer, keith.
>
> https://cs.stanford.edu/~keithw/tack-sigcomm2020.pdf
>
> --
> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
next prev parent reply other threads:[~2021-10-20 10:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 20:12 [Make-wifi-fast] " Dave Taht
2021-10-19 20:25 ` [Make-wifi-fast] [Rpm] " Matt Mathis
2021-10-19 20:31 ` Omer Shapira
2021-10-20 7:00 ` [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 ` [Make-wifi-fast] [Rpm] " 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 ` Sebastian Moeller [this message]
2021-10-20 11:55 ` Toke Høiland-Jørgensen
2021-10-20 20:37 ` Sebastian Moeller
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D464EE6A-CB65-41F0-BA70-BCFE4DA4ECC1@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 \
/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