From: Maciej Soltysiak <maciej@soltysiak.com>
To: Aaron Wood <woody77@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] a new chipset and elsewhere a review of streamboost
Date: Fri, 24 Jan 2014 13:28:33 +0100 [thread overview]
Message-ID: <CAMZR1YBcjOr-jkhavdzEPenXy9kjKqvVx_amS0aGcG-GPBm2vQ@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-N0qdvw0UMVsgXdTvkMEW==oBMhN=1HGxmTiA9z4Xn3wQ@mail.gmail.com>
Couldn't find a mention of *codel, but it would be sad to see vendors
just sprinkle some traffic shaping on top of codel and brand it.
It cheers me up that *codel is about to be picked up by the vendors,
but not when customers are tricked to pay extra for SuperBoostNow [tm]
or DoMeQuick [tm]...
--
Maciej
On Fri, Jan 24, 2014 at 1:06 PM, Aaron Wood <woody77@gmail.com> wrote:
> It would be interesting to see what streamboost gains on top of just
> fq_codel. Since it appears that they are doing so fairly heavy-handed
> traffic shaping.
>
> -Aaron
>
>
> On Fri, Jan 24, 2014 at 12:48 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> An interesting new chipset:
>>
>>
>> http://www.anandtech.com/show/7526/qualcomm-atheros-announces-new-internet-processor-lineup-ipq8064-and-ipq8062
>>
>> And streamboost (of which fq_codel is a component) is getting good
>> reviews:
>>
>>
>> http://www.smallnetbuilder.com/lanwan/lanwan-features/32297-does-qualcomms-streamboost-really-work?start=1
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt:
>> http://www.teklibre.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
next prev parent reply other threads:[~2014-01-24 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 11:48 Dave Taht
2014-01-24 12:06 ` Aaron Wood
2014-01-24 12:28 ` Maciej Soltysiak [this message]
2014-01-24 13:15 ` Dave Taht
2014-01-24 18:29 ` dpreed
2014-01-24 23:54 ` 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/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=CAMZR1YBcjOr-jkhavdzEPenXy9kjKqvVx_amS0aGcG-GPBm2vQ@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@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