From: Dave Taht <dave.taht@gmail.com>
To: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Dashboard dedicated to BufferBloat issue
Date: Fri, 21 Sep 2012 08:07:48 -0700 [thread overview]
Message-ID: <CAA93jw579KrxTH5FebmHP71jia1zk6gg3KJ-jSreoCrZk=9GdA@mail.gmail.com> (raw)
In-Reply-To: <505C70B7.9070608@etorok.net>
On Fri, Sep 21, 2012 at 6:50 AM, Török Edwin
<edwin+ml-cerowrt@etorok.net> wrote:
> On 09/21/2012 12:09 PM, Branco Camporeto wrote:
>> Hey you Guys,
>>
>> I'm French (sorry for my english...) and I'm working for a MSO. Thank you very much for your work, I appreciate.
>>
>> I already warned my company about the bad QoS due to Bufferbloat issue. I've got some skills in cable networks and I already did a technical note for upgrading the buffer control feature inside cmts
>> and cable modem.
I'd like to see that tech note...
>> For helping me and tracking all events about bufferbloat, I did this public dashboard. http://www.netvibes/bufferbloat
>> I keep updating it.
Very cool page. We have something of a problem in that solutions that
we had last year (shortening txqueue length and reducing tx rings)
have been replaced by much better ones (byte queue limits (BQL)), and
fq_codel, and various web sites still have obsolete advice (including
ours). And the solutions we have today don't work well on wireless as
yet, and more improvements are pending all over the stack, and the BSD
work is just beginning...
>>
>> If you have twitter accounts to track, hot url, newsgroups...etc I can aggregate them.
>
> There were a few videos posted earlier on this ML that should probably be there:
> https://lists.bufferbloat.net/pipermail/bloat/2012-September/001066.html
> https://lists.bufferbloat.net/pipermail/bloat/2012-September/001068.html
>
> --Edwin
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"
next prev parent reply other threads:[~2012-09-21 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 9:09 Branco Camporeto
2012-09-21 10:46 ` Jan Ceuleers
2012-09-21 13:50 ` Török Edwin
2012-09-21 15:07 ` Dave Taht [this message]
2012-09-26 13:08 ` Branco
2012-09-24 13:18 ` Branco
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='CAA93jw579KrxTH5FebmHP71jia1zk6gg3KJ-jSreoCrZk=9GdA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=edwin+ml-cerowrt@etorok.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