Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net, Justin Beech <justinbeech@gmail.com>,
	Kathleen Nichols <nichols@pollere.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat]  dslreports and inbound rate shaping
Date: Thu, 21 May 2015 20:41:52 -0700	[thread overview]
Message-ID: <CALQXh-Ng8oh9CTQ4oZXJUeHkEBrYR6zC5=6H1EQwVsgXsPEuug@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE0sTV-NhVvo+q-FCQFo50kB=CCZ6GktfJCdkK-2Tnmb2Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

But will it trigger at all?  If the inbound rate is say 50Mbps, and the
link to the in-home devices are over 100Mbps ethernet, will codel _ever_
see a 5ms buffer on inbound?

Or is the shaping buffering incoming packets, and creating a bundle that it
can measure?  (I don't know the internals of how htb(?) does the limiting)

-Aaron

On Thu, May 21, 2015 at 9:39 AM, Jonathan Morton <chromatix99@gmail.com>
wrote:

> No - at 90% shaping on ingress, 5/5ms will trigger when the visible queue
> has built up to 5ms over a continuous 50ms.  At 95%, it'll trigger at 100ms.
>
> Remember, Codel can't see what's in the dumb FIFO on the upstream end of
> the link. By the time it triggers, there's potentially a lot of queue there
> that it doesn't know about and can't directly measure. That's why it has to
> be more aggressive about the queue it can see.
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>

[-- Attachment #2: Type: text/html, Size: 1646 bytes --]

  reply	other threads:[~2015-05-22  3:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 19:17 [Cake] " Dave Taht
2015-05-21 16:21 ` Jonathan Morton
2015-05-21 15:07   ` [Cake] [Bloat] " Kathleen Nichols
2015-05-21 15:26     ` Jonathan Morton
2015-05-21 16:31       ` Kathleen Nichols
2015-05-21 16:39         ` Jonathan Morton
2015-05-22  3:41           ` Aaron Wood [this message]
2015-05-22  6:32             ` Jonathan Morton
2015-05-25 11:26 ` Mikael Abrahamsson

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALQXh-Ng8oh9CTQ4oZXJUeHkEBrYR6zC5=6H1EQwVsgXsPEuug@mail.gmail.com' \
    --to=woody77@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=justinbeech@gmail.com \
    --cc=nichols@pollere.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