Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Daniel Havey <dhavey@gmail.com>
Cc: cake@lists.bufferbloat.net,
	Alan Jenkins <alan.christopher.jenkins@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] [Cake] active sensing queue management
Date: Fri, 12 Jun 2015 21:34:45 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1506122131580.24535@nftneq.ynat.uz> (raw)
In-Reply-To: <CAO1c0AQfnNq-8V6Bfw+2z+Z_7ZDPKbtML4-jc==F3BddU6sYqw@mail.gmail.com>

On Fri, 12 Jun 2015, Daniel Havey wrote:

>> ii) Sebastian points out if you implement AQSM in the modem (as the paper
>> claims :p), you may as well BQL the modem drivers and run AQM.  *But that
>> doesn't work on ingress* - ingress requires tbf/htb with a set rate - but
>> the achievable rate is lower in peak hours. So run AQSM on ingress only!
>> Point being that download bloat could be improved without changing the other
>> end (CMTS).
>>
> This is pretty cool.  I had not considered BQL (though Dave and Jim
> were evangelizing about it at the time :).  This solves the
> upload/download problem which I was not able to get past in the paper.
> BQL on the egress and ASQM for the ingress.  BQL will make sure that
> the upload is under control so that ASQM can get a good measurement on
> the download side.  Woot!  Woot!  Uncooperative ISP problem solved!
>
> BTW...Why doesn't BQL work on the ingress?

for the same reason that AQM doesn't work on inbound connections. you're on the 
wrong side of the link :-)

implementing AQM and BQL on the ISPs device that's sending to the home user is 
a perfectly reasonable thing to do and is really the right answer for the 
problem.

all the rest of this is a matter of "we can't get at where the problem really is 
to fix it, so let's figure out what else we can do to mitigate the problem"

David Lang

  parent reply	other threads:[~2015-06-13  4:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 19:53 [Cerowrt-devel] " Dave Taht
2015-06-10 20:54 ` [Cerowrt-devel] [Cake] " Sebastian Moeller
2015-06-11  0:10   ` Daniel Havey
2015-06-11  7:27     ` Sebastian Moeller
2015-06-12 15:02       ` Daniel Havey
2015-06-12 16:02         ` Sebastian Moeller
2015-06-12  1:49     ` David Lang
2015-06-12 14:44       ` Daniel Havey
2015-06-13  4:00         ` David Lang
2015-06-13  5:50           ` Benjamin Cronce
2015-06-11  1:05   ` Alan Jenkins
2015-06-11  7:58     ` Sebastian Moeller
2015-06-12  1:44       ` [Cerowrt-devel] [Bloat] " David Lang
2015-06-12  9:52         ` MUSCARIELLO Luca IMT/OLN
2015-06-12 16:51           ` Benjamin Cronce
2015-06-13  4:16             ` David Lang
2015-06-12 12:18         ` Sebastian Moeller
2015-06-12 13:00           ` Alan Jenkins
2015-06-12 14:35             ` Daniel Havey
2015-06-12 17:55               ` Alan Jenkins
2015-06-13  4:34               ` David Lang [this message]
2015-06-13  4:30           ` David Lang
2015-06-13  5:37             ` [Cerowrt-devel] [Cake] [Bloat] " Benjamin Cronce

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=alpine.DEB.2.02.1506122131580.24535@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dhavey@gmail.com \
    /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