Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cake] quad core arm
Date: Sun, 3 Dec 2017 11:49:59 -0800	[thread overview]
Message-ID: <CAA93jw7gWb=rkNoqW=xjTiiayFyG4urEzKenCdpwUSYOCh3yAg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw43M=dhPOFhMJo7f-qOq=k=kKS6ppq4o9=hsTEKoBdUpA@mail.gmail.com>

https://www.solid-run.com/marvell-armada-family/armada-8040-community-board/

looks rather promising. (recommendation courtesy koen koi)

I also picked up two 30 dollar 10GigE interfaces for spaceheater and
whatever I end up calling the second box

https://www.amazon.com/gp/product/B016OYD0D4/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1

I guess in part what I'm mentally shifting to, is what happens after
cake? I'd rather like to have something an ISP could use on or near a
head end, and that entails moving stuff into hardware (and a few more
O(1) algorithms).

Mellonox at least used to make a board with hackable FPGAs, and
perhaps marvell will be more open about how to program the offload
engine next time, and P4 is coming along.


On Sun, Dec 3, 2017 at 9:44 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I have gone through a lot of hackerboards in the last few years.
>
> I had multiple goals for them - primarily I wanted cheap and
> cheap-to-power wifi and ethernet test targets. I settled on the
> c.h.i.p. for a while for wifi.
>
> Another goal was a largely fruitless quest to find the ideal next gen
> replacement for the wndr3800. These days I'm using a AC2600 as my main
> device and waiting for the ath10k support to catch up. I used to use
> an olimex something or other for my NAS, I upgraded it to a pine64,
> which was better but crashed hard a few months ago and I've not had a
> chance to go fix it.
>
> In most cases getting a modern kernel was a major problem. The odroid
> C2 was my fastest network test target (can't drive 1gbit bidir tho),
> and stuck on linux 3.10 for several years now. (I've heard rumors 4.x
> almost works now).
>
> Anyway the nanopi folk are now producing a wide range of boards I
> haven't tried... til tomorrow:
>
> https://www.amazon.com/gp/product/B0728LPB2R/ref=oh_aui_detailpage_o00_s01?ie=UTF8&psc=1
>
> These appear to be supported on modern kernels in armbian (which has
> thus far been the "best" distro for these hackerboards for me).
>
> https://www.armbian.com/nanopi-neo-2/
>
> On the really high end the 48 core arm boxes from cavium look interesting.
>
> Anything else worth looking at?
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  parent reply	other threads:[~2017-12-03 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 17:44 Dave Taht
2017-12-03 18:18 ` [Cake] [Cerowrt-devel] " Joel Wirāmu Pauling
2017-12-03 19:49 ` Dave Taht [this message]
2017-12-04  0:19   ` Michael Richardson
2017-12-04  0:11 ` Michael Richardson
2017-12-04  0:34   ` Joel Wirāmu Pauling

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='CAA93jw7gWb=rkNoqW=xjTiiayFyG4urEzKenCdpwUSYOCh3yAg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@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