Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] still trying to find hardware for the next generation worth hacking on
Date: Fri, 15 Aug 2014 13:33:16 -0700	[thread overview]
Message-ID: <CAA93jw5T_cdzhQ1h=VUAE7KsC5xGhwbsUQZPiUr1EoecmHhjyg@mail.gmail.com> (raw)

I figure everyone has already seen this:

http://burntchrome.blogspot.com/2014/05/fixing-bufferbloat-on-comcasts-blast.html

But this is the best we can do. Above 50mbit, cero's current hardware
(cpu designed in 1989)
peaks out. We've done some testing on the slightly higher end
edgerouter lite, and it
can't keep up, either, above about 70mbit. The edgerouter pro does
considerably better but costs considerably more. ivy bridge x86 boxes
"just work" up to well past 300mbits...

As cerowrt 3.10 is basically baked, it's time (finally!) to find a new
chipset that everyone can work with, and move on to higher gateway
bandwidths, and 802.11ac.

For 2+ years now, we've been looking for better hardware than this...
and I'd like to at
least find something sooner that could run the SQM system at 105Mbit...

I know we could just switch future development to intel hardware, and
there are some promising arm based designs now out, and there have
been a few suggestions here and on cerowrt-devel...

At the moment, I'm thinking that instead of searching for a chipset,
and board, that merely issuing an RFP with the requirements of this
project and others associated with it, might find us a vendor willing
to help, with something new coming off the line... would anyone be
interested in helping write that?

-- 
Dave Täht

             reply	other threads:[~2014-08-15 20:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 20:33 Dave Taht [this message]
2014-08-15 20:51 ` [Cerowrt-devel] [Bloat] " Eric S. Raymond
2014-08-15 21:02   ` Dave Taht
2014-08-15 21:21     ` Jonathan Morton
2014-08-16  0:46       ` David P. Reed
2014-08-16 20:41       ` Michael Richardson
2014-08-17 17:13     ` dpreed
2014-08-17 17:43       ` William Katsak
2014-08-18 20:51       ` Frank Carmickle
2014-08-18 22:00         ` Dave Taht
2014-08-19  0:34           ` Michael Richardson
2014-08-22  3:11       ` Dave Taht
2014-08-22 13:16         ` Chuck Anderson
2014-08-22 13:32         ` William Katsak
2014-08-22 14:19           ` David P. Reed
2014-08-22 15:12             ` William Katsak
2014-08-22 20:20               ` dpreed
2014-08-22 20:39         ` [Cerowrt-devel] " Wes Felter
2014-08-18 19:19     ` [Cerowrt-devel] [Bloat] " Wes Felter
2014-08-18 20:09       ` Aaron Wood
2015-03-09 12:53     ` Guillaume Fortaine
2015-03-09 13:11       ` Sebastian Moeller

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='CAA93jw5T_cdzhQ1h=VUAE7KsC5xGhwbsUQZPiUr1EoecmHhjyg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --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