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,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] active sensing queue management
Date: Thu, 11 Jun 2015 18:49:16 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1506111845300.16013@nftneq.ynat.uz> (raw)
In-Reply-To: <CAO1c0ARWWwu8yu7tEuBD+Lh2qu5b4Ts5qanaNBSyf9hnu1ptQw@mail.gmail.com>

On Wed, 10 Jun 2015, Daniel Havey wrote:

> We know that (see Kathy and Van's paper) that AQM algorithms only work
> when they are placed at the slowest queue.  However, the AQM is placed
> at the queue that is capable of providing 8 Mbps and this is not the
> slowest queue.  The AQM algorithm will not work in these conditions.

so the answer is that you don't deploy the AQM algorithm only at the perimeter, 
you deploy it much more widely.

Eventually you get to core devices that have multiple routes they can use to get 
to a destination. Those devices should notice that one route is getting 
congested and start sending the packets through alternate paths.

Now, if the problem is that the aggregate of inbound packets to your downstreams 
where you are the only path becomes higher than the available downstream 
bandwidth, you need to be running an AQM to handle things.

David Lang


  parent reply	other threads:[~2015-06-12  1:49 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 [this message]
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
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.1506111845300.16013@nftneq.ynat.uz \
    --to=david@lang.hm \
    --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