From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Dave Taht <dave.taht@gmail.com>,
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 13:34:59 +1300 [thread overview]
Message-ID: <CAKiAkGRHkCRoteVZ9qHWDdLkDqQ6emmr=sdd2Gs2DJ3TkvopQQ@mail.gmail.com> (raw)
In-Reply-To: <23960.1512346289@obiwan.sandelman.ca>
On 4 December 2017 at 13:11, Michael Richardson <mcr@sandelman.ca> wrote:
>
> Dave Taht <dave.taht@gmail.com> wrote:
.
>
> > On the really high end the 48 core arm boxes from cavium look interesting.
>
> I'm told that there is some special sauce to get them to go at the speeds the
> specs say. Basically you run Linux on one core, and a special (binary blob)
> micro kernel on the other 47, and manage them via FORCES.
>
Can confrim; we included a Cavium GPC in our Original VSG7850 as a
Linux Environment along side the Trident2+ chipset.
It was a nightmare just getting the NDK signed to get access to the
Cavium build chain, and then it was using an ancient 2.6 kernel with
Secret sauce patches.
prev parent reply other threads:[~2017-12-04 0:35 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 ` [Cake] [Cerowrt-devel] " Joel Wirāmu Pauling
2017-12-03 19:49 ` [Cake] " 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 [this message]
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='CAKiAkGRHkCRoteVZ9qHWDdLkDqQ6emmr=sdd2Gs2DJ3TkvopQQ@mail.gmail.com' \
--to=joel@aenertia.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=mcr@sandelman.ca \
/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