Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Simon Barber <simon@superduper.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
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: Thu, 30 Nov 2017 14:59:41 -0800	[thread overview]
Message-ID: <97FED3CC-CFF8-47EE-987B-81771EDB6128@superduper.net> (raw)
In-Reply-To: <F03A75BA-B098-4F4F-99E1-84BBC2F9C56E@toke.dk>

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.

Simon

> On Nov 30, 2017, at 2:50 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 
> 
> 
> On 30 November 2017 23:35:33 CET, Simon Barber <simon@superduper.net> wrote:
>> This was our assumption (client = endpoint, 802.11 ACK = TCP delivery),
>> but we discovered that this is not always the case, even where the
>> client is the endpoint. FastACK keeps the data around and retransmits
>> it in this case.
> 
> Ah. So that means you have something very close to a full TCP
> state machine in the AP?
> 
> -Toke


  reply	other threads:[~2017-11-30 22:59 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 [this message]
2017-12-01 12:48               ` Toke Høiland-Jørgensen
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=97FED3CC-CFF8-47EE-987B-81771EDB6128@superduper.net \
    --to=simon@superduper.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@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