Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] risc-v options?
Date: Tue, 30 Nov 2021 16:33:35 -0800	[thread overview]
Message-ID: <CAA93jw6fFdNyYbaQvurmbOfbZ1m8D4TPQAhr7=7mmOzK97zPvQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4RgTEra_Z9pasXVZgf6Ez5pMUub2gkAjGK-tQ6nXucjA@mail.gmail.com>

also, a 2.5ghz, 16 core chip was open sourced last month.

https://www.cnx-software.com/2021/10/20/alibaba-open-source-risc-v-cores-xuantie-e902-e906-c906-and-c910/

On Tue, Nov 30, 2021 at 4:23 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> On Tue, Nov 30, 2021 at 2:52 PM David P. Reed <dpreed@deepplum.com> wrote:
> >
> > For what?
>
> Because it's shiny. Because I don't care for the owner of softbank and
> arm very much. Because at least the core is open source, and I'd
> really like to try out some long held ideas about reducing context
> switch latency. And there's a couple instructions I'd like to add.
>
> >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.
>
> how fast can it context switch? (irtt bench)
>
> I am impressed that it works with anything on pcie.
>
> I was mostly dismissing risc-v as a toy that could never catch up to
> arm 3 years ago, but with the enormous chinese investment in it...
>
> >
> >
> > 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.
>
> Intel has always had an advantage in on-chip cache.
>
> >
> >
> >
> > (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).
>
> I don't find 32 bit risc-v interesting. I did fiddle with the 128 bit
> risc-v stuff for a while.
>
> >
> >
> > A random guess on my part: even consumer routers will be moving to 64-bit processor designs in the next couple years.
>
> Many already have.
>
> > 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.
>
> 802.11ax standards require - no joke - a 2MByte buffer per station.
>
> >
> >
> >
> >
> >
> > 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
> > >
>
>
>
> --
> 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



-- 
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

  reply	other threads:[~2021-12-01  0:33 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
2021-12-01  0:23   ` Dave Taht
2021-12-01  0:33     ` Dave Taht [this message]
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='CAA93jw6fFdNyYbaQvurmbOfbZ1m8D4TPQAhr7=7mmOzK97zPvQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.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