From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Cc: mikel.irazabal@upc.edu
Subject: [Bloat] Preventing RLC Buffer Sojourn Delays in 5G
Date: Sun, 28 Nov 2021 16:33:51 -0800 [thread overview]
Message-ID: <CAA93jw4YdKZXoQtr3UucwqvsJdYVKbGG2LUypvn_BNFXApwghg@mail.gmail.com> (raw)
A nice comparison of BBR vs Codel vs FIFO vs their cross-layer
solution. (they used irtt!)
I am always puzzled as to why folk don't benchmark fq-codel (or
something like BQL)
in scenarios like these. Are the headers not available in the RAN?
(forgive me for forgetting)
Anyway, their "vanilla" scenario shows 5G with > 1sec of buffering.
Is that real?
https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9369375
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2021-11-29 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 0:33 Dave Taht [this message]
2021-11-29 10:28 ` Mikel Irazabal Bengoa
2021-11-29 12:02 ` Dave Taht
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=CAA93jw4YdKZXoQtr3UucwqvsJdYVKbGG2LUypvn_BNFXApwghg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=mikel.irazabal@upc.edu \
/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