From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jan Ceuleers <jan.ceuleers@gmail.com>,
bloat@lists.bufferbloat.net,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Bloat] benefits of ack filtering
Date: Fri, 01 Dec 2017 13:53:51 +0100 [thread overview]
Message-ID: <87wp2638yo.fsf@toke.dk> (raw)
In-Reply-To: <6b494910-1373-afb0-5b93-99b725391fb3@gmail.com>
Jan Ceuleers <jan.ceuleers@gmail.com> writes:
> On 01/12/17 01:28, David Lang wrote:
>> Stop thinking in terms of single-flow benchmarks and near idle
>> 'upstream' paths.
>
> Nobody has said it so I will: on wifi-connected endpoints the upstream
> acks also compete for airtime with the downstream flow.
There's a related discussion going on over on the make-wifi-fast list
related to the FastACK scheme proposed by Meraki at this year's IMC:
https://conferences.sigcomm.org/imc/2017/papers/imc17-final203.pdf
It basically turns link-layer ACKs into upstream TCP ACKs (and handles
some of the corner cases resulting from this) and also seems to contain
an ACK compression component.
-Toke
next parent reply other threads:[~2017-12-01 12:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw47ZAXAJmiOVCb2NR3JRcCfmX0TLr+55O0G+J6HCW5bVQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.20.1711290655590.32099@uplift.swm.pp.se>
[not found] ` <4D0E907C-E15D-437C-B6F7-FF348346D615@gmx.de>
[not found] ` <alpine.DEB.2.20.1711291347050.32099@uplift.swm.pp.se>
[not found] ` <CAHx=1M7=ig-S-iQ_Fj2f-KMoa-QUVu1DZ4HyfWybvQiGeBb1GQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.20.1711291528260.32099@uplift.swm.pp.se>
[not found] ` <CAHx=1M77XYX9t6J_zG1oArOze1-nTRPB9bNQLRfwFRZjH3mQjQ@mail.gmail.com>
[not found] ` <7B92DF4D-B6B5-4A64-9E10-119DCA2D4A6F@ifi.uio.no>
[not found] ` <CAJq5cE36bErJGDQQutpFgbENmiN9SvSc+bVXJ-BmZ9S_Jv3joA@mail.gmail.com>
[not found] ` <1512037480.19682.10.camel@gmail.com>
[not found] ` <alpine.DEB.2.20.1711301343320.32099@uplift.swm.pp.se>
[not found] ` <alpine.DEB.2.02.1711301623270.2950@nftneq.ynat.uz>
[not found] ` <6b494910-1373-afb0-5b93-99b725391fb3@gmail.com>
2017-12-01 12:53 ` Toke Høiland-Jørgensen [this message]
2017-12-01 13:13 ` Кирилл Луконин
2017-12-01 13:22 ` Luca Muscariello
2017-12-11 17:42 ` Simon Barber
2017-12-01 13:17 ` Luca Muscariello
2017-12-01 13:40 ` Toke Høiland-Jørgensen
2017-12-01 17:42 ` Dave Taht
2017-12-01 20:39 ` Juliusz Chroboczek
2017-12-03 5:20 ` Bob McMahon
2017-12-03 10:35 ` Juliusz Chroboczek
2017-12-03 19:04 ` Bob McMahon
2017-12-01 21:17 ` Bob McMahon
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=87wp2638yo.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=jan.ceuleers@gmail.com \
--cc=make-wifi-fast@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