From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Definitional Jiu-jitsu (was Re: 3.10.32-12 results on Free.fr)
Date: Tue, 1 Apr 2014 14:45:39 -0400 [thread overview]
Message-ID: <6F81B5BF-B7CC-40B7-9793-FCF62B735881@gmail.com> (raw)
In-Reply-To: <CAA93jw6HrytJt-BuSsak=uSZkQgO4qefWP+q7UzgXCWEmBPADg@mail.gmail.com>
On Apr 1, 2014, at 2:21 PM, Dave Taht <dave.taht@gmail.com> wrote:
> One thing I've noticed is the academic community is now seemingly defining
> "bufferbloat" as something that happens with > 200ms induced queuing
> delay delay, where I (we) define it as "excessive queueing", and in
> this group, are "settling" for <20ms delay in both directions in most
> cases.
Hmmm... The academic community has finally come to understand the concept, and use the name "bufferbloat". Maybe that's OK, even if their understanding is dramatically different from ours.
Perhaps this is an opportunity to let their momentum fully embrace the Brobdignagian notion that 200 msec is OK, while we pivot agilely to use something like "smarterqueue.net" to define the "real good" scheme?
I'm not sure we have the gravitas to pull this off, but it's worth considering.
Rich
PS I can envision the soundtrack in the Youtube video...
... (stirring music) ...
... From the team that conquered Bufferbloat...
... Comes a technique that smashes it by an order of magnitude...
... (trumpets)...
A fitting idea for a fitting day :-)
next prev parent reply other threads:[~2014-04-01 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 10:21 [Cerowrt-devel] 3.10.32-12 results on Free.fr Aaron Wood
2014-04-01 18:21 ` Dave Taht
2014-04-01 18:45 ` Rich Brown [this message]
2014-04-01 21:08 ` [Cerowrt-devel] Definitional Jiu-jitsu (was Re: 3.10.32-12 results on Free.fr) Toke Høiland-Jørgensen
2014-04-02 6:57 ` [Cerowrt-devel] 3.10.32-12 results on Free.fr Aaron Wood
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6F81B5BF-B7CC-40B7-9793-FCF62B735881@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@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