From: Pete Heist <pete@eventide.io>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] I have no idea how this got published...
Date: Thu, 7 Jun 2018 12:38:07 +0200 [thread overview]
Message-ID: <F2C2750F-BCAC-4089-A9C1-9D5D110CCFBD@eventide.io> (raw)
In-Reply-To: <87y3fsevrv.fsf@toke.dk>
> On Jun 6, 2018, at 12:03 AM, 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…
Just after a quick read, I fail to see how just decreasing buffer sizes is going to be “better”. Better than just throwing fq_codel on the wireless interface, maybe.
In regards to CoDel and PIE, they say "both of these schemes never consider frame aggregation in the buffer sizing decision.” Isn’t the whole point of CoDel that one doesn’t need to be concerned with buffer size as long as it’s “large enough”?
> 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.
That’s arm waving that really misrepresents the work without even testing it.
> I am mildly outraged…
Is there a better place to respond than adding a comment to the article?
next prev parent reply other threads:[~2018-06-07 10:38 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
2018-06-05 22:49 ` Dave Taht
2018-06-07 10:38 ` Pete Heist [this message]
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=F2C2750F-BCAC-4089-A9C1-9D5D110CCFBD@eventide.io \
--to=pete@eventide.io \
--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