From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bloat goes away, but with ~25% speed loss?
Date: Fri, 5 Jun 2015 18:20:14 +0100 [thread overview]
Message-ID: <5571DA4E.5060809@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw6CqNnRarHru=6YxSAgj01V34OHh8gjxLBhdsRYUKCJ=Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1368 bytes --]
On 05/06/2015 17:19, Dave Taht wrote:
> On Fri, Jun 5, 2015 at 7:33 AM, Kevin Darbyshire-Bryant
> <kevin@darbyshire-bryant.me.uk> wrote:
>>
>> On 04/06/15 21:01, Jonathan Morton wrote:
>>
>> A useful exercise might be to log the idle latency over a long period of
>> time, and correlate it to peak load periods, as A&A do.
>> http://aa.net.uk/kb-broadband-cqm.html .
>>
>> Minor claim to 'infamy'. The line graph shown on that page is my ADSL line
>> from 4ish years ago :-) I was having a hell of a time trying to convince BT
>> to solve the packet loss issue caused by a faulty PSU in a satellite
>> receiver (one whole street away and affecting a LOT of people) Andrews &
>> Arnold (ISP) were the only people capable of hitting BT with a sufficiently
>> large cluebat.
> A&A struck me as an extremely clueful ISP (I think they have had ipv6
> /48s for forever?)
> and it has been my impression that folk like that were using things
> like HFSC + SFQ already
> in their "rate limiters", and had experimented also with fq_codel by now.
Adrian Kennard the owner writes code for their ISP grade routers etc (Firebricks). Very clever chap. And yes very early adopters and promoters of IPv6. No idea what qdiscs etc they've experimented with. I'll try to ask. Would be interesting to get fq_codel or even cake into the ISP side of things!
[-- Attachment #1.2: 0x9DE2334A.asc --]
[-- Type: application/pgp-keys, Size: 3596 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-05 17:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 21:18 Rich Brown
2015-06-04 20:01 ` Jonathan Morton
2015-06-05 14:33 ` Kevin Darbyshire-Bryant
2015-06-05 16:19 ` Dave Taht
2015-06-05 17:20 ` Kevin Darbyshire-Bryant [this message]
2015-06-05 17:23 ` Dave Taht
2015-06-05 17:25 ` Adrian Kennard
2015-06-05 17:27 ` Adrian Kennard
2015-06-05 17:44 ` Kevin Darbyshire-Bryant
2015-06-05 17:48 ` Dave Taht
2015-06-05 17:51 ` Adrian Kennard
2015-06-05 17:57 ` Kevin Darbyshire-Bryant
2015-06-05 17:59 ` Adrian Kennard
2015-06-05 19:44 ` Dave Taht
2015-06-05 20:06 ` Dave Taht
2015-06-05 22:45 ` jb
2015-06-05 22:52 ` Dave Taht
[not found] ` <55722786.7090904@hp.com>
2015-06-06 0:32 ` jb
2015-06-06 0:40 ` Rick Jones
2015-06-06 3:54 ` Aaron Wood
2015-06-06 4:13 ` jb
2015-06-06 8:45 ` Kevin Darbyshire-Bryant
2015-06-06 9:30 ` jb
2015-06-06 10:04 ` Kevin Darbyshire-Bryant
2015-06-06 10:22 ` jb
2015-06-04 23:32 ` Aaron Wood
2015-06-04 23:38 ` Rick Jones
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=5571DA4E.5060809@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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