From: David Lang <david@lang.hm>
To: Luca Muscariello <luca.muscariello@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] On the 802.11 performance anomaly and an airtime fairness scheduler to fix it
Date: Sun, 3 Jul 2016 00:06:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1607030003501.18304@nftneq.ynat.uz> (raw)
In-Reply-To: <CAHx=1M4UyVU6PwVB8wF2p94dDpgPZdo1Ci_jwhRM5CEOBR6ydg@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 651 bytes --]
On Sun, 3 Jul 2016, Luca Muscariello wrote:
> Toke,
>
> great piece of work.
> UDP tests show that the scheduler is working quite well.
> TCP tests: no news that ACK streams are a problem.
> This is another well known issue in wifi.
>
> Every data packet is ACKed already at L2 and L4
> sends an ACK that is non contention free.
>
> There is an NSDI paper in 2014 that proposes to use the L2 ACK to carry the
> L4 ACK.
> It works well but purists might hate that approach.
do they delay the L2 Ack until the L4 ack comes back? If so, how does that work
on long-latency connections where it takes a long time for the L4 ack to show
up?
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 167 bytes --]
_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/make-wifi-fast
next prev parent reply other threads:[~2016-07-03 7:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 21:06 Toke Høiland-Jørgensen
2016-07-01 13:31 ` Sebastian Moeller
2016-07-01 23:10 ` Dave Taht
2016-07-02 10:26 ` Dave Taht
2016-07-03 6:55 ` Luca Muscariello
2016-07-03 7:06 ` David Lang [this message]
2016-07-03 7:50 ` Jonathan Morton
2016-07-03 7:53 ` Luca Muscariello
2016-07-03 8:03 ` David Lang
2016-07-03 9:07 ` Jonathan Morton
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=alpine.DEB.2.02.1607030003501.18304@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=luca.muscariello@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