From: Michael Richardson <mcr@sandelman.ca>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [aqm] DOCSIS 3.1 support for AQM
Date: Thu, 31 Oct 2013 10:32:49 -0400 [thread overview]
Message-ID: <29158.1383229969@obiwan.sandelman.ca> (raw)
In-Reply-To: <CALQXh-NBWoeCOt_CS65c3NKM3p_cs19a+BjBUi+qzb2j8UF7=w@mail.gmail.com>
Has any one any analysis of having sfq_codel on the CPE (uplink) stream,
and PIE on the CMTS (downlink) stream?
I'm assuming that the two directions should not conflict, but given that
RTT estimates and congestion signals involve bidirectional traffic, maybe
this assumption is wrong.
I also want to suggest that the fairness considerations of the household
are not necessarily the same as the fairness considerations of the ISP.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
next prev parent reply other threads:[~2013-10-31 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 20:13 [Bloat] " Greg White
2013-10-31 8:25 ` [Bloat] [aqm] " Bless, Roland (TM)
2013-10-31 13:23 ` Aaron Wood
2013-10-31 14:32 ` Michael Richardson [this message]
2013-11-04 23:20 ` Greg White
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=29158.1383229969@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bloat@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