From: Sebastian Moeller <moeller0@gmx.de>
To: bloat@lists.bufferbloat.net,
Jonathan Morton <chromatix99@gmail.com>,
valdis.kletnieks@vt.edu
Cc: cerowrt-devel@lists.bufferbloat.net,bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] Invisibility of bufferbloat and its remedies
Date: Wed, 20 Jun 2018 01:47:08 +0200 [thread overview]
Message-ID: <95BB2E1A-BD8C-4D30-8C6C-6F17EE84AD55@gmx.de> (raw)
In-Reply-To: <C59F7661-C0C3-4017-A582-8E804E7D044D@gmail.com>
On June 20, 2018 1:41:19 AM GMT+02:00, Jonathan Morton <chromatix99@gmail.com> 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.
Well many ISPs nowadays employ additional traffic shapers upstream of the dslam/MSAN, and it is this shaper's set-rate we would need to have. All we know is that this needs to be <= sync but the details differ. Also we need information about per packet overhead which again is not easily available for end-users. IMHO our best bet would be to get regulatory agancies to force ISPs to make this information easily available to end-users so that customers can actually compare different offers realistically, but I am not holding my breath for this to happen in my lifetime...
Best Regards
Sebastian
>
>On wireless links, all bets are off - even with stationary endpoints,
>link capacity varies wildly over time. This needs to be solved in the
>radio-modems.
>
>If it's wifi, however, a link-rate-independent solution now exists for
>certain hardware, and there's nothing theoretically stopping something
>similar being put into future HardMAC implementations. If we get the
>choice of hardware, naturally we choose wisely.
>
> - Jonathan Morton
>
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2018-06-19 23:47 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 [this message]
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=95BB2E1A-BD8C-4D30-8C6C-6F17EE84AD55@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@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