From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] I have no idea how this got published...
Date: Wed, 06 Jun 2018 00:31:17 +0200 [thread overview]
Message-ID: <D66B8C0F-F3FE-4470-B58F-EC48A226C6E0@toke.dk> (raw)
In-Reply-To: <CAA93jw41RRa=VNnbudby-WLp-+wWCevvEp57QgA01ZWQytMRMg@mail.gmail.com>
Whaddyamean correct? They don't actually test against our work, if that's what you mean...
On 6 June 2018 00:23:02 CEST, Dave Taht <dave.taht@gmail.com> wrote:
>well, are the results correct?
>
>On Tue, Jun 5, 2018 at 3:03 PM, Toke Høiland-Jørgensen <toke@toke.dk>
>wrote:
>> https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8359288
>>
>> They change buffer sizes (but dynamically!) and manage to do better
>than
>> Linux with CoDel and PIE as qdiscs on the WiFi interface. Linux
>3.17.7,
>> that is. This was published today...
>>
>> What's worse is that they actually cite our paper, with this comment:
>>
>>> Recently, Høiland-Jørgensen et al. [20] also tackled bufferbloat in
>>> APs with the goal to reduce latency and improve airtime fairness.
>>> Their proposal was built on top of FQ-CoDel which is one of the
>>> queuing disciplines in Linux. We believe that the mesh environment
>>> imposes further challenges that are not addressed in this work.
>>
>> I am mildly outraged...
>>
>> -Toke
>> _______________________________________________
>> 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:[~2018-06-05 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 22:03 Toke Høiland-Jørgensen
2018-06-05 22:23 ` Dave Taht
2018-06-05 22:31 ` Toke Høiland-Jørgensen [this message]
2018-06-05 22:49 ` Dave Taht
2018-06-07 10:38 ` Pete Heist
2018-06-07 11:54 ` 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=D66B8C0F-F3FE-4470-B58F-EC48A226C6E0@toke.dk \
--to=toke@toke.dk \
--cc=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