From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Simon Barber <simon@superduper.net>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Dave Taht <dave.taht@gmail.com>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Fwd: Re: [iccrg] TCP behavior across WiFi pointers ?
Date: Fri, 01 Dec 2017 13:48:19 +0100 [thread overview]
Message-ID: <87374u4nsc.fsf@toke.dk> (raw)
In-Reply-To: <97FED3CC-CFF8-47EE-987B-81771EDB6128@superduper.net>
Simon Barber <simon@superduper.net> writes:
> Certain things, yes, others - not so much. No congestion control for
> example. It’s very much the common case that the wireless client is
> the TCP endpoint, and it’s rare to see drops, but they do happen.
> FastACK keeps the TCP ACK rate controlled by the wireless bandwidth,
> unlike a proxy. This is the key innovation here.
Right, actually went and read the paper now. Seems clear enough; a few
questions, though:
- From figure 12 it looks like you are also implicitly doing ACK
compression? I.e., if you get two packets with seq n and n+1 you will
only send an ACK back to the sender for n+1?
- Did you measure the latency impact of FastACK? You mention you will do
that once it's deployed, but does that mean you didn't measure this at
all in the testbed?
-Toke
next prev parent reply other threads:[~2017-12-01 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 7:39 Toke Høiland-Jørgensen
2017-11-30 8:04 ` Dave Taht
2017-11-30 8:07 ` Dave Taht
2017-11-30 8:21 ` Jonathan Morton
2017-11-30 8:52 ` Toke Høiland-Jørgensen
2017-11-30 22:35 ` Simon Barber
2017-11-30 22:50 ` Toke Høiland-Jørgensen
2017-11-30 22:59 ` Simon Barber
2017-12-01 12:48 ` Toke Høiland-Jørgensen [this message]
2017-12-01 14:57 ` Dave Taht
2017-11-30 9:03 ` 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=87374u4nsc.fsf@toke.dk \
--to=toke@toke.dk \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=simon@superduper.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