From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] SQM Question #1: How does SQM shape the ingress?
Date: Sat, 28 Dec 2013 23:31:33 -0500 [thread overview]
Message-ID: <B42663E5-D044-4CC5-9546-C5FF14E02575@gmail.com> (raw)
As I write the SQM page, I find I have questions that I can’t answer myself. I’m going to post these questions separately because they’ll each generate their own threads of conversation.
QUESTION #1: How does SQM shape the ingress?
I know that fq_codel can shape the egress traffic by discarding traffic for an individual flow that has dwelt in its queue for too long (greater than the target). Other queue disciplines use other metrics for shaping the outbound traffic.
But how does CeroWrt shape the inbound traffic? (I have a sense that the simple.qos and simplest.qos scripts are involved, but I’m not sure of anything beyond that.)
next reply other threads:[~2013-12-29 4:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 4:31 Rich Brown [this message]
2013-12-29 7:23 ` Sebastian Moeller
2013-12-29 7:57 ` Dave Taht
2013-12-29 11:28 ` 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=B42663E5-D044-4CC5-9546-C5FF14E02575@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