Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cake] [Cerowrt-devel] quad core arm
Date: Mon, 4 Dec 2017 07:18:02 +1300	[thread overview]
Message-ID: <CAKiAkGTL4ojHxk0JZrdkKv1S9RcoNJ4yEb-_oPsjMdvvBx91Dg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw43M=dhPOFhMJo7f-qOq=k=kKS6ppq4o9=hsTEKoBdUpA@mail.gmail.com>

I quite liked the rk3399 board ; it has enough lanes for good duplex
ethernet support, but I haven't seen anyone bundling with multiple
Gigabit ports on a board so you are stuck with miniPciE add-in or USB3
dongles for more than one port.

You can get hold of them relatively easily via aliexpress and there
was a crowdfunded 'tinker' board variant out
:http://wiki.t-firefly.com/index.php/Firefly-RK3399/en

In addition to the rockchip board any of the sunxi - allwinner boards
have had a lot of mainline support added over the last 6 months. Most
of the easily available boards are all geared towards HTPC
applications however.

My current interest is in the c3xxx platform which FINALLY has enough
oomph to do duplex 20gbit and can be had with SFP+ equipped variants.

Lately most of the testing work I have been doing has been with the
thunderbolt3 network driver in net-next (and which I think is tagged
for inclusion with 4.15) which gives you 10-40gbit networking mostly
hasslefree.


-Joel





On 4 December 2017 at 06:44, 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

  reply	other threads:[~2017-12-03 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 17:44 [Cake] " Dave Taht
2017-12-03 18:18 ` Joel Wirāmu Pauling [this message]
2017-12-03 19:49 ` Dave Taht
2017-12-04  0:19   ` [Cake] [Cerowrt-devel] " 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=CAKiAkGTL4ojHxk0JZrdkKv1S9RcoNJ4yEb-_oPsjMdvvBx91Dg@mail.gmail.com \
    --to=joel@aenertia.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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