From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] risc-v options?
Date: Tue, 30 Nov 2021 17:52:35 -0500 (EST) [thread overview]
Message-ID: <1638312755.776218387@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6GAOJh-RrvvJtC339U6PV_S+GeBLttqY=bkv3tQ2V4Jg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
For what? I have recently gotten a MicroSemi RISC-V SoC board with embedded FPGA (or maybe it is better thought of as an FPGA board with multicore hard logic RISC-V host.) Runs Linux very fast. It's not set up to be a router, though - not unless I populate its PCIe slot with NICs. Standard Linux drivers for PCIe devices all work quite well, so far.
These early 64 bit RISC-V implementations are pretty darn good, but unlike Intel's Xeons, they don't yet handle memory channel performance very well.
(The 32-bit RISC-V's are really competing with ARM based microcontrollers for embedded systems. I don't find them interesting, though I have a couple sample boards with 32 bit RISC-V cores).
A random guess on my part: even consumer routers will be moving to 64-bit processor designs in the next couple years. That's because the price difference is getting quite small, as a percentage of total product cost, and because it is hard to buy "small memory address space" DIMMs. I could be wrong, but extrapolation from today's trends suggests that is more likely than not.
On Friday, November 26, 2021 3:02pm, "Dave Taht" <dave.taht@gmail.com> said:
> has anyone tried the latest generations of risc-v?
>
> https://linuxgizmos.com/17-sbc-runs-linux-on-allwinner-d1-risc-v-soc/
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2937 bytes --]
next prev parent reply other threads:[~2021-11-30 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 20:02 Dave Taht
2021-11-30 22:52 ` David P. Reed [this message]
2021-12-01 0:23 ` Dave Taht
2021-12-01 0:33 ` Dave Taht
2021-12-01 4:50 ` Dave Taht
2021-12-01 16:57 ` Arun Ray Ramadorai
[not found] ` <mailman.983.1638392349.1267.cerowrt-devel@lists.bufferbloat.net>
2021-12-01 21:36 ` John Yates
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=1638312755.776218387@apps.rackspace.com \
--to=dpreed@deepplum.com \
--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