General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Zili Meng <zilim@ieee.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "gyn17@tsinghua.org.cn" <gyn17@tsinghua.org.cn>,
	孙晨 <qichen.sc@alibaba-inc.com>, 徐明伟老师 <xumw@tsinghua.edu.cn>,
	"Bo Wang" <wangbo2019@tsinghua.edu.cn>,
	"Justine Sherry" <sherry@cs.cmu.edu>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	lampson0505@gmail.com
Subject: Re: [Bloat] Achieving Consistent Low Latency for Wireless Real-Time Communications with the Shortest Control Loop
Date: Wed, 27 Jul 2022 17:14:57 -0400	[thread overview]
Message-ID: <CAPZHne1sc-ZQmtJsk1a163y_OmYcjHvJ8mGk478KL6aS6-CGdg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7X0sbFwdRSxzzUaTA60L8q4tG-BGbcDyzLKGBgO9qJkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]

Hi Dave,

Sorry for the late reply. Thank you for your interest in our work! And also
thank you so much for providing the pointers on related literature! They
are really helpful and we will look into these work later.

We did simulate the FqCoDel using the built-in implementation of ns-3. Two
of the issues that we found are that (i) some CCAs are not responsive to
packet losses, especially for latency-sensitive CCAs -- GCC seems to need a
loss rate of >10% to trigger the loss controller; and (ii) if the CCA on
the sender is not ECN-compatible, additional packet retransmissions will
further occupy the buffer space, leading to longer duration of congestion.

We did not compare FqCoDel in the testbed experiments on WiFi AP due to the
reasons above. We do hope to test with more cases and baselines in the real
implementations in the future.

If there are any further questions, please do not hesitate to contact us.
Thank you!

On Sat, Jul 9, 2022 at 6:08 PM Dave Taht <dave.taht@gmail.com> wrote:

> While I deeply appreciate y'all citing our work in this paper,
>
> https://zilimeng.com/papers/zhuge-sigcomm22.pdf
>
> it's not clear if the AP with your solution was actually
> fq_codeled[1]? We've also been battling a ton of regressions of late.
>
> PS It was good to see confirmation of long-tail latency at 99th
> percentile over 400ms in such a large study of gaming users.
>
> PPS Perhaps this paper would be of use?
> https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8469111
>
> [1] https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002/621
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
>


-- 
Cheers,
----------------
Zili Meng
Web: https://zilimeng.com

[-- Attachment #2: Type: text/html, Size: 3879 bytes --]

      reply	other threads:[~2022-07-27 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 22:08 Dave Taht
2022-07-27 21:14 ` Zili Meng [this message]

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPZHne1sc-ZQmtJsk1a163y_OmYcjHvJ8mGk478KL6aS6-CGdg@mail.gmail.com \
    --to=zilim@ieee.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=gyn17@tsinghua.org.cn \
    --cc=lampson0505@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=qichen.sc@alibaba-inc.com \
    --cc=sherry@cs.cmu.edu \
    --cc=wangbo2019@tsinghua.edu.cn \
    --cc=xumw@tsinghua.edu.cn \
    /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