From: Luca Muscariello <luca.muscariello@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: David Lang <david@lang.hm>,
"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 09:53:52 +0200 [thread overview]
Message-ID: <CAHx=1M7z2tag=Sek_5i4G9yHtH-vom+VmK1E1DubkB_cQs1-fg@mail.gmail.com> (raw)
In-Reply-To: <EEF37B16-8B8A-40E9-9AC6-91F43B167025@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
https://www.usenix.org/system/files/conference/atc14/atc14-paper-salameh.pdf
The paper I mentioned.
Usenix ATC'14 not NSDI.
On Sunday, 3 July 2016, Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 3 Jul, 2016, at 10:06, David Lang <david@lang.hm <javascript:;>>
> wrote:
> >
> > 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?
>
> I’m pretty sure it’s only meant to work when the TCP endpoint is local to
> the receiving station, assuring low turnaround latency. This is the
> typical case, so it’s a win.
>
> With that said, there’s no fundamental reason why the piggybacked L4 ack
> need be the one corresponding to the L2 ack. It just needs to be a small
> packet that won’t unduly extend the airtime occupied by the ack anyway, and
> which won’t mind being lost if the L2 ack gets squashed. A scheme allowing
> a certain amount of slop in this way would accommodate remote TCP endpoints
> as well as local ones.
>
> - Jonathan Morton
>
>
[-- Attachment #2: Type: text/html, Size: 1551 bytes --]
next prev parent reply other threads:[~2016-07-03 7:53 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
2016-07-03 7:50 ` Jonathan Morton
2016-07-03 7:53 ` Luca Muscariello [this message]
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='CAHx=1M7z2tag=Sek_5i4G9yHtH-vom+VmK1E1DubkB_cQs1-fg@mail.gmail.com' \
--to=luca.muscariello@gmail.com \
--cc=chromatix99@gmail.com \
--cc=david@lang.hm \
--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