From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cerowrt-devel] Invisibility of bufferbloat and its remedies
Date: Wed, 20 Jun 2018 17:57:42 +0200 [thread overview]
Message-ID: <67ee54f6-444e-1568-3419-23c434792157@gmail.com> (raw)
In-Reply-To: <C59F7661-C0C3-4017-A582-8E804E7D044D@gmail.com>
On 20/06/18 01:41, Jonathan Morton wrote:
>> On 19 Jun, 2018, at 11:34 pm, valdis.kletnieks@vt.edu wrote:
>>
>> Do we have a good cookbook on how to determine the set-rate?
>
> On DSL, the sync rates in each direction should usually be readable from the modem; they are typically reported on the router's status page. The advertised rate is less reliable, to say the least.
I'm afraid that my DSL modem doesn't belong to the "usually" case. I
have a BBox3 from Proximus (Belgium). Proximus buys these from two
manufacturers: Technicolor and Sagemcom. I have the Sagemcom variant.
Proximus went out of their way to avoid that end users be able to query
the modem for its connection parameters. There is still an indirect way
to do so in the Sagemcom variant (and so I know that my modem provides
50Mbit/s down and 10Mbit/s up) but for marketing reasons Proxinus would
prefer its users not to know. The reason is that their principal
competitor, cable operator Telenet (owned by Liberty Global) would win
the game based on raw link speed.
So whereas I have access to the information I need to be able to
configure my queues there are others who do not, and it would be good
for a generic method to exist that derives the correct parameters from
measurements.
Kathy put it more succinctly: there is a good case for monitoring.
Question is what to monitor and how to set/modify the qdisc parameters.
Jan
next prev parent reply other threads:[~2018-06-20 15:57 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
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 [this message]
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=67ee54f6-444e-1568-3419-23c434792157@gmail.com \
--to=jan.ceuleers@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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