From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: mikel <irazabal@eurecom.fr>
Subject: [Cerowrt-devel] Dynamic Buffer Sizing and Pacing as Enablers of 5G Low-Latency Services
Date: Fri, 14 Jan 2022 08:58:15 -0800 [thread overview]
Message-ID: <CAA93jw6h8Jvad6Qy29jX0XBpNAxuN26eMmp7cevwXy=+xTx6cw@mail.gmail.com> (raw)
There have been, oh, 3? papers or so that I thought were good on how
to do queuing more right on 5G networks, out of the hundreds. I'm
pretty
sure I posted a couple of the most promising ones here, but cannot
remember enough (today my head is filled with gpon) of wading through
the alphabet soup for the right ones that
had had the serious AHA moments over the past couple years.
this went by today, which looks kind of promising:
https://sci-hub.se/10.1109/TMC.2020.3017011
As much as I am pleased with the progress of the sqm-autorate work ,
dang it, our stuff belongs closer to the hardware.
--
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
reply other threads:[~2022-01-14 16:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6h8Jvad6Qy29jX0XBpNAxuN26eMmp7cevwXy=+xTx6cw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=irazabal@eurecom.fr \
/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