From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] SQM Question #2: How does CeroWrt use info gleaned from the link layer adaptation?
Date: Sat, 28 Dec 2013 23:32:23 -0500 [thread overview]
Message-ID: <3AE6C690-F53C-471F-9980-9E071B87D983@gmail.com> (raw)
QUESTION #2: How does CeroWrt use info gleaned from the link layer adaptation?
Specifically, the link layer adaptation all seem to be designed to compute the actual time it takes to transmit a packet, accounting for Ethernet & PPPoE header bytes, other overhead, and ATM 48-in-53 framing.
How does CeroWrt use this time calculation? Does it simply make sure that the target time doesn’t get too low for a particular flow’s queue? (I could imagine that a short packet over ATM would take 2x the (naive) expected/calculated time for a packet of that length, and that flow would be penalized. Is there more to it?)
next reply other threads:[~2013-12-29 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 4:32 Rich Brown [this message]
2013-12-29 7:36 ` Sebastian Moeller
2013-12-29 8:54 ` Dave Taht
2013-12-29 10:52 ` Fred Stratton
2013-12-29 13:51 ` Sebastian Moeller
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=3AE6C690-F53C-471F-9980-9E071B87D983@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@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