From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Detecting FQ at the bottleneck
Date: Sun, 25 Oct 2020 16:06:35 +0100 [thread overview]
Message-ID: <87k0ve5oqs.fsf@toke.dk> (raw)
This popped up in my Google Scholar mentions:
https://arxiv.org/pdf/2010.08362
It proposes using a delay-based CC when FQ is present, and a loss-based
when it isn't. It has a fairly straight-forward mechanism for detecting
an FQ bottleneck: Start two flows where one has 2x the sending rate than
the other, keep increasing their sending rate until both suffer losses,
and observe the goodput at this point: If it's ~1:1 there's FQ,
otherwise there isn't.
They cite 98% detection accuracy using netns-based tests and sch_fq.
-Toke
next reply other threads:[~2020-10-25 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 15:06 Toke Høiland-Jørgensen [this message]
2020-10-25 18:51 ` David Collier-Brown
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=87k0ve5oqs.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@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