From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
debayani.ghosh@thapar.edu, ee11s040@ee.iitm.ac.in,
gaurav@ee.iitm.ac.in
Subject: [Bloat] why do people still study RED?
Date: Wed, 31 May 2023 16:28:14 -0600 [thread overview]
Message-ID: <CAA93jw7QmcD+kgM_BxWnhDC9_4ag5BHP-tp4SGvu_mTZDGsgwg@mail.gmail.com> (raw)
An otherwise good paper on RED vs drop tail here:
https://arxiv.org/pdf/2303.10220.pdf
Is it because we completely lack any analytical methods for taking a
hard look at drop or marking from the head, as codel does, or the
effect of the fq in fq_codel?
I keep hoping somehow, somewhere, someone would show up with the tools
to explain the results I got here:
https://blog.cerowrt.org/post/juniper/
--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
next reply other threads:[~2023-05-31 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 22:28 Dave Taht [this message]
2023-05-31 23:03 ` Stephen Hemminger
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=CAA93jw7QmcD+kgM_BxWnhDC9_4ag5BHP-tp4SGvu_mTZDGsgwg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=debayani.ghosh@thapar.edu \
--cc=ee11s040@ee.iitm.ac.in \
--cc=gaurav@ee.iitm.ac.in \
/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