From: Pete Heist <peteheist@gmail.com>
To: erik.taraldsen@telenor.com
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Recomended HW to run cake and fq_codel?
Date: Wed, 3 May 2017 20:05:20 +0200 [thread overview]
Message-ID: <F8B062C9-5C1C-4D03-9613-67BDC7DA8631@gmail.com> (raw)
In-Reply-To: <mailman.1.1493827201.27042.cake@lists.bufferbloat.net>
> Message: 6
> Date: Wed, 3 May 2017 11:14:14 +0000
> From: <erik.taraldsen@telenor.com>
> To: <moeller0@gmx.de>
> Cc: <me@lochnair.net>, <cake@lists.bufferbloat.net>
> Subject: Re: [Cake] Recomended HW to run cake and fq_codel?
> Message-ID: <1493810054966.42941@telenor.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
>> Fra: Sebastian Moeller <moeller0@gmx.de>
>> Well, compared to most on this list you have a huge impact on the chipset vendors, so I hope for the best.
>> Is there anybode besides Broadcom and Intel actually producing VDSL chipsets or is that the set of vendors
>> that need to be convinced?
>
> There are other chipset vendors, but they have very little precense in the west. They typically aim for super low-cost volum in Asia. Pure bridge units which in extreme cases can't push packets trough at sync speed. So for all intents and purposes I think the focus for DSL has to be Broadcom and Intel.
If someone takes the time to write a petition, I would sign it as I’m sure would others. Delivered to the right people (the other tricky part), it could mean something. I feel the same way about Cake on the ER-X.
next parent reply other threads:[~2017-05-03 18:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1493827201.27042.cake@lists.bufferbloat.net>
2017-05-03 18:05 ` Pete Heist [this message]
[not found] <mailman.1.1493740801.18318.cake@lists.bufferbloat.net>
2017-05-02 18:44 ` Pete Heist
2017-05-03 5:59 ` erik.taraldsen
2017-05-03 7:15 ` Pete Heist
2017-05-03 10:03 ` Andy Furniss
2017-05-03 11:10 ` erik.taraldsen
2017-11-27 8:35 ` Dave Taht
2017-11-27 12:04 ` Jonathan Morton
2017-11-27 12:47 ` Pete Heist
2017-11-27 15:54 ` Sebastian Moeller
2017-11-27 16:12 ` Pete Heist
2017-11-27 18:28 ` Jonathan Morton
2017-11-27 21:49 ` Pete Heist
[not found] <mailman.430.1493386395.3609.cake@lists.bufferbloat.net>
2017-04-28 16:39 ` Lochnair
2017-05-02 10:34 ` erik.taraldsen
2017-05-02 12:11 ` Nils Andreas Svee
2017-05-02 17:36 ` David Lang
2017-05-03 5:36 ` erik.taraldsen
2017-05-03 6:51 ` Sebastian Moeller
2017-05-03 7:27 ` erik.taraldsen
2017-05-03 8:24 ` Sebastian Moeller
2017-05-03 11:14 ` erik.taraldsen
[not found] ` <mailman.433.1493397541.3609.cake@lists.bufferbloat.net>
2017-04-28 18:07 ` Tristan Seligmann
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F8B062C9-5C1C-4D03-9613-67BDC7DA8631@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=erik.taraldsen@telenor.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