Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] trouble on tid 5
Date: Mon, 18 Apr 2016 20:47:38 -0700	[thread overview]
Message-ID: <CAA93jw4ygNbjNUuRAAuo1nrkbkG0tenSAgsk0seWu9JKcgQwHA@mail.gmail.com> (raw)

I had been testing ath9k a bit with fq_codel a bit with patch tim
supplied me, and I noticed an issue with the VI queue. Might be across
more queues than that, but definately VI.

examples see around packet number 4394, 8638, and like 139144 - in the cap:

http://www.taht.net/~d/carnage.cap.gz

the essential dialog:

station: Here you go, frames 60 through 68. (IP x.y.19.15)

AP: (IP x.y.18.1) I didn't get frames 78-123

station: Here you go, frames 60 through 68, at a different rate:

AP no, you idiot! I didn't get frames 78-123

The cycle repeats XX times for a total of YY microsecs, before the
driver gives up...

I did not poke much further, thought I'd supply an aircap so folk
could look at what one looked like.  Me, all I wanted to do was fiddle
with the Ack Policy field but haven't got to it yet.

...

data generated via aircapping a rrul test between tim's fq_codel patch
and a cerowrt box. The box seemingly misunderstanding the AP is tim's
side....

...


The worst part of this is that' it all for acks. All we had to do to
keep the tcp flow going was 1 ack - frame XX, and tcp would have
handled it ok...

-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

                 reply	other threads:[~2016-04-19  3:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw4ygNbjNUuRAAuo1nrkbkG0tenSAgsk0seWu9JKcgQwHA@mail.gmail.com \
    --to=dave.taht@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