From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Dave Taht <dave@taht.net>,
make-wifi-fast@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat] benefits of ack filtering
Date: Sat, 2 Dec 2017 21:20:33 -0800 [thread overview]
Message-ID: <CAHb6Lvr9YFgNagNKo5tq7fcN9=Go4xjx2R6fx98hYZWE0tSjHA@mail.gmail.com> (raw)
In-Reply-To: <87shcui3ni.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
I'm skeptical that this would improve single stream throughput by a factor
of two. The larger RTT would drive larger aggregations and it's
aggregation that scales peak average throughput.
Also, the time difference between the 802.11 ack and the client network
stack writing the TCP ack would probably be in the 100s of microseconds
(mileage will vary.) So it's the client's media access that will drive the
increase in RTT. It might be preferred to modify EDCA parameters to
reduce media access latencies for TCP acks rather than spoof them.
Bob
On Fri, Dec 1, 2017 at 12:39 PM, Juliusz Chroboczek <jch@irif.fr> wrote:
> >> It does increase single-flow TCP throughput by up to a factor of two,
> >> though... Which everyone knows is the most important benchmark number ;)
>
> > Were you always as cynical as I am?
>
> (Giggle)
>
> Dave, you've always underestimated Toke ;-)
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
[-- Attachment #2: Type: text/html, Size: 1679 bytes --]
next prev parent reply other threads:[~2017-12-03 5:20 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
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 [this message]
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='CAHb6Lvr9YFgNagNKo5tq7fcN9=Go4xjx2R6fx98hYZWE0tSjHA@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=jch@irif.fr \
--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