Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: Eric Raymond <esr@thyrsus.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] still trying to find hardware for the next generation worth hacking on
Date: Sun, 17 Aug 2014 13:13:33 -0400 (EDT)	[thread overview]
Message-ID: <1408295613.063215615@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6MntHVbTT4n_-bGm7Das3-kDseCJiR=WzTT6zpY06s1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]


[ http://www.habeyusa.com/products/fwmb-7950-rangeley-network-communication-board/ ]( http://www.habeyusa.com/products/fwmb-7950-rangeley-network-communication-board/ ) looks intriguing.
 
Probably a bit pricey, but has lots of advantages.  There's another smaller one that might do:
 
[ http://www.habeyusa.com/products/fwmb-7935/ ]( http://www.habeyusa.com/products/fwmb-7935/ )
 
both are intel based, but for Linux that means that you don't have to deal with all the issues of non-intel instruction sets.


On Friday, August 15, 2014 5:02pm, "Dave Taht" <dave.taht@gmail.com> said:



> On Fri, Aug 15, 2014 at 1:51 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
> > Dave Taht <dave.taht@gmail.com>:
> >> 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?
> >
> > I can do critical reader and style editor. If other people generate
> > a content-complete rough draft I can beat it into something slick and
> > persuasive.
> 
> Eric: That would be a big help, TIA!
> 
> one promising project is this one: https://www.turris.cz/en/
> 
> but it would make more sense to port the needed software (bql,
> fq_codel, sqm) over
> to it first and do some benchmarking before committing to using it and
> getting it manufactured in more volume.
> 
> > --
> > <a href="http://www.catb.org/~esr/">Eric S.
> Raymond</a>
> 
> 
> 
> --
> Dave Täht
> 
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 

[-- Attachment #2: Type: text/html, Size: 3312 bytes --]

  parent reply	other threads:[~2014-08-17 17:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 20:33 [Cerowrt-devel] " Dave Taht
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 [this message]
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=1408295613.063215615@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=esr@thyrsus.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