General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Frank Carmickle <frank@carmickle.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] still trying to find hardware for the next generation worth hacking on
Date: Mon, 18 Aug 2014 17:00:45 -0500	[thread overview]
Message-ID: <CAA93jw7eq7D=xR4_KgY1s9y+3LBJhLFUpXdsEc7ZaYtDWOKh_w@mail.gmail.com> (raw)
In-Reply-To: <EF616CA3-4BC1-45A7-860C-54D4DB7A6F1D@carmickle.com>

On Mon, Aug 18, 2014 at 3:51 PM, Frank Carmickle <frank@carmickle.com> wrote:
>
> On Aug 17, 2014, at 1:13 PM, dpreed@reed.com wrote:
>
> http://www.habeyusa.com/products/fwmb-7950-rangeley-network-communication-board/
> looks intriguing.
>
>
> This, and others like it from Supermicro and Asrock, are what I am
> interested in.  I'm not so sure this is what Dave is looking for.  These are
> not sub $100 boards by any stretch.  I happen to like IPMI serial over LAN
> and don't really want to live without it.  I built a Habey fanless chassis
> and a Asrock board system with 16gb of RAm a few months ago.  The Habey
> fanless chassis is pretty nice except that it smelled awful.  They have an
> external inline power brick with a barrel connector that is converted to atx
> by a small board in the chassis.  This way I also get to run Debian without
> worrying about filling up some small flash.
>
> Dave, are you looking for something for the masses?

No, I'm looking for something to do further, open, effective, bleeding
edge and game changing research on... a project that will run for
another 3+ years...

...that eventually will be something for the masses.

Cost is not a huge object right now. Cheap in 3 years would be a good goal.

On the high end, for example, are things like netfpga, and lower cost
options like the parallella architecture.

http://netfpga.org/
http://www.parallella.org/

It does seem like better hardware offloads need to be developed to ensure that
rate scheduling, AQM, and fair queuing, can move into new hardware.

I agree with other folk on this thread that we are in a transition
period where the cost-effective chips have offloads that interfere
with further bufferbloat related research, even on the technologies
that are relatively open (ethernet, wifi).

This situation is far worse on access technologies such as 3g, and
lte, cable, and gpon, which are black boxes out of reach of open and
academic researchers.

About the only FTTH technology that is relatively accessible is single
mode fiber ethernet, and it appears to be uncommon except in
municipalities that have mandated ISP competition (for example:
http://arstechnica.com/tech-policy/2010/03/how-amsterdam-was-wired-for-open-access-fiber/
)

In the cases where we can make a difference, the only cpu technologies
that appear
capable of doing GigE and software rate limiting and codel seem to be
x86 based. (And only intel! even a amd box, recently benchmarked,
couldn't forward at > 700Mbit)

I even have doubts about the atom box mentioned earlier, the available
cache sizes are quite small, and ivy bridge based platforms seem
better, but only testing could tell.

Although I like the turrus project, I too am dubious about the future
for power pc in these marketplace.

I've had a chat with atheros about some of their new stuff, I'm not
sure what of that I can share here (yet). Will let you all know when I
can.

I think all options are open. I'd like to have a project that could
indeed be funded (for a change!) - AND make a difference - and be fun
and useful for everyone here and a variety of other research-y
projects like project bismark, the EFF work, commotion wireless, etc,
etc. An ideal project would be to produce an entirely open high speed
router that anyone could make.

Shorter term... it would be nice to find a board that "just worked"
well with the SQM system, up to 300mbit, however. That covers the
largest band of ISP deployments for the next several years.

And I, at least, have competing goals - there are the gateway problem,
and the DSLAM/CMTS/GPON head end problem... and then there's fixing
wifi, which is nearest and dearest to my heart.

At the moment I'm planning on switching to some x86 box to prototype
solutions for make-wifi-fast, (due to ease of debugging mostly,
availability of mini-pcie, also). 802.11ac is presently a mess...

So I appreciate the suggestions so far, keep them coming! All options
are on the table and what we'll congeal on or not congeal on is wildly
variable, but I would like to find a way focus enough folk on solving
any one problem to get decent results inside of a year.

Note: I am at sigcomm and linuxcon this week in chicago and my replies
will be sparse.

My morning's keynote at the congestion control workshop slides are up at:

http://snapon.lab.bufferbloat.net/~d/sigcomm2014.pdf

(Sadly, not recorded)




>
> --FC
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-08-18 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 20:33 [Bloat] " Dave Taht
2014-08-15 20:51 ` Eric S. Raymond
2014-08-15 21:02   ` Dave Taht
2014-08-15 21:21     ` Jonathan Morton
2014-08-16  0:46       ` [Bloat] [Cerowrt-devel] " David P. Reed
2014-08-16 20:41       ` [Bloat] " Michael Richardson
2014-08-17 17:13     ` [Bloat] [Cerowrt-devel] " dpreed
2014-08-18 20:51       ` Frank Carmickle
2014-08-18 22:00         ` Dave Taht [this message]
2014-08-19  0:34           ` Michael Richardson
2014-08-22  3:11       ` Dave Taht
     [not found]     ` <lstjkh$k82$1@ger.gmane.org>
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/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='CAA93jw7eq7D=xR4_KgY1s9y+3LBJhLFUpXdsEc7ZaYtDWOKh_w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=frank@carmickle.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