From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Jan Ceuleers <jan.ceuleers@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ultrafast broadband conference june 27-30
Date: Sat, 18 Jun 2016 07:07:59 -0700 [thread overview]
Message-ID: <CAA93jw4eHE9fdiA8Wi+q=NX7fAAUkNd=99O=MyeHsqVGdjP5+A@mail.gmail.com> (raw)
In-Reply-To: <4685FAFC-D406-4BD5-B37C-2E0AFDD2D410@gmail.com>
On Sat, Jun 18, 2016 at 6:55 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 18 Jun, 2016, at 14:22, Jan Ceuleers <jan.ceuleers@gmail.com> wrote:
>>
>> Would it be worth pursuing an RFC on how to properly test the
>> performance of an internet access circuit and/or of a path across an IP
>> network? RFC compliance might be a tool to get Ookla to take notice.
My answer has become to try to "get in the face" of more existing
standards bodies working at these layers.
Before that, it was "find a way to sit down with the actual driver
developer to go make these *very simple* changes to the underlying
firmware blob". A BQL-like technique is *not rocket science*. My
estimate was less than 3 days worth of engineering for someone
familiar with the firmware source, coupled with someone familiar with
the queue theory.
Merely limiting the maximum number of packets queued in the firmware
to 2x what is needed for interleave at that rate to work, is even
simpler, if less effective.
> I think that could happen, if someone sits down and drafts one. The “AQM Characterization Guidelines” one is coming along nicely, and is obviously related.
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-06-18 14:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 16:05 Dave Taht
2016-06-15 5:43 ` Pedro Tumusok
2016-06-18 8:04 ` Jan Ceuleers
2016-06-18 10:09 ` Jonathan Morton
2016-06-18 10:20 ` Jan Ceuleers
2016-06-18 10:24 ` Jonathan Morton
2016-06-18 10:38 ` Jan Ceuleers
2016-06-18 10:51 ` Toke Høiland-Jørgensen
2016-06-18 11:06 ` Jan Ceuleers
2016-06-18 11:14 ` Toke Høiland-Jørgensen
2016-06-18 11:22 ` Jan Ceuleers
2016-06-18 13:55 ` Jonathan Morton
2016-06-18 14:07 ` Dave Taht [this message]
2016-06-18 13:31 ` 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='CAA93jw4eHE9fdiA8Wi+q=NX7fAAUkNd=99O=MyeHsqVGdjP5+A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=jan.ceuleers@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