General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Holland, Jake" <jholland@akamai.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] datapoint from one vendor regarding bloat
Date: Thu, 11 Apr 2019 23:56:10 +0000	[thread overview]
Message-ID: <ACA7922F-7CBD-4441-AC79-096B67723F90@akamai.com> (raw)
In-Reply-To: <6889A853-52F2-4554-9450-F59F9CB6B91A@gmail.com>

On 2019-04-11, 11:29, "Jonathan Morton" <chromatix99@gmail.com> wrote:
> A question I would ask, though, is whether that 10ms automatically scales to the actual link rate, or whether it is pre-calculated for the fastest rate and then actually turns into a larger time value when the link rate drops.  That's a common fault with sizing FIFOs, too.

That's an interesting question and maybe a useful experiment, if somebody's
got one of these boxes.

But in practice do you expect link speed changes to be a major issue?  Would
this just be an extra point that should also be tuned if the max link speed is
changed dramatically by config and the policer is turned on (so there's, say, a
5% increased chance of misconfig and a reasonably diagnosable problem that a
knowledgebase post somewhere would end up covering once somebody's dug into it),
or is there a deeper problem if it's pre-calculated for the fastest rate?

-Jake



  reply	other threads:[~2019-04-11 23:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 10:38 Mikael Abrahamsson
2019-04-11 12:45 ` Sebastian Moeller
2019-04-11 17:33   ` Sebastian Moeller
2019-04-11 17:54 ` Jonathan Morton
2019-04-11 18:00   ` Holland, Jake
2019-04-11 18:28     ` Jonathan Morton
2019-04-11 23:56       ` Holland, Jake [this message]
2019-04-12  0:37         ` Jonathan Morton
2019-04-12  0:45           ` Holland, Jake
2019-04-12  9:47       ` Mikael Abrahamsson
2019-04-11 18:02   ` Jan Ceuleers
2019-04-11 18:27   ` Luca Muscariello

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=ACA7922F-7CBD-4441-AC79-096B67723F90@akamai.com \
    --to=jholland@akamai.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=swmike@swm.pp.se \
    /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