General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: cerowrt-devel@lists.bufferbloat.net, valdis.kletnieks@vt.edu,
	Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] Invisibility of bufferbloat and its remedies
Date: Wed, 20 Jun 2018 01:32:43 +0200	[thread overview]
Message-ID: <4D964A33-9AEC-4F5F-94C9-5A1FE430F2E2@gmx.de> (raw)
In-Reply-To: <145517.1529440447@turing-police.cc.vt.edu>

Well,

On June 19, 2018 10:34:07 PM GMT+02:00, valdis.kletnieks@vt.edu wrote:
>On Mon, 18 Jun 2018 18:46:18 -0700, Dave Taht said:
>
>> One of cake's "minor" features is the *perfect* defeat of the htb
>> based shaper in cable modems. If you know the set-rate on the modem,
>> you just set it to the same thing and get vastly superior performance
>to
>> docsis 3.1, pie, or the sqm-scripts.
>
>Do we have a good cookbook on how to determine the set-rate?

With cable <DOCSIS 3.1 one can Snoop the management frames that will also carry the bandwidth definitions. Or with a compromised cable modem one could dump the DOCSIS config file that also contains that information. Or ask the ISP. Short of any of that one could run a umber of speedtests over a 24 hour period and simply extrapolate from the measured goodput to the required 'gross' DOCSIS shaper rate:

Measured TCP/ipv4 goodput * ((1518)/(1500-20-20)) = lower bound gross bandwidth estimate

DOCSIS employs a shaper to limit user's exceeding the contracted rates, that per DOCSIS standard assumes 1518 bytes of accountable raw frame size. Tangent that 1518 obviously is a 'lie' in that it does not include all per packet overhead in use on a DOCSIS carrier, but from an end-user perspective that difference is immaterial...

I realize that you probably wanted something simpler and more accurate, sorry to disappoint.

Best Regards
        Sebastian



>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2018-06-19 23:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 16:26 [Bloat] " dpreed
2018-06-18 19:07 ` Dave Taht
2018-06-18 22:43   ` dpreed
2018-06-18 23:17     ` Jonathan Morton
2018-06-19  2:21       ` dpreed
2018-06-19  1:46     ` Dave Taht
2018-06-19 19:33       ` Dave Taht
2018-06-19 19:45         ` dpreed
2018-06-19 20:34       ` [Bloat] [Cerowrt-devel] " valdis.kletnieks
2018-06-19 23:32         ` Sebastian Moeller [this message]
2018-06-20  6:56           ` [Bloat] (no subject) Sebastian Moeller
2018-06-20 14:03             ` Kathleen Nichols
2018-06-20 14:07             ` Kathleen Nichols
2018-06-19 23:41         ` [Bloat] [Cerowrt-devel] Invisibility of bufferbloat and its remedies Jonathan Morton
2018-06-19 23:47           ` Sebastian Moeller
2018-06-20  7:12           ` Kevin Darbyshire-Bryant
2018-06-20  8:07             ` Sebastian Moeller
2018-06-20  9:15               ` Kevin Darbyshire-Bryant
2018-06-20  9:34                 ` Sebastian Moeller
2018-06-20 15:57           ` Jan Ceuleers
2018-06-20 17:27             ` Sebastian Moeller
2018-06-18 20:59 ` Michael Richardson
2018-06-18 21:14   ` Dave Taht

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=4D964A33-9AEC-4F5F-94C9-5A1FE430F2E2@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=valdis.kletnieks@vt.edu \
    /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