From: John Yates <john@yates-sheets.org>
To: Arun Ray Ramadorai <ray@ramadorai.org>
Cc: Dave Taht <dave.taht@gmail.com>,
"David P. Reed" <dpreed@deepplum.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] risc-v options?
Date: Wed, 1 Dec 2021 16:36:05 -0500 [thread overview]
Message-ID: <CAJnXXohK6AsnzTJCHK=SnYjQJ9L53Bg86hKL_R-pqg3NRp0sTQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.983.1638392349.1267.cerowrt-devel@lists.bufferbloat.net>
On Wed, Dec 1, 2021 at 3:59 PM Arun Ray Ramadorai
via Cerowrt-devel <cerowrt-devel@lists.bufferbloat.net> wrote:
>
> Architecturally I would say it is still about 8yrs behind ARM.
> Cache performance, power management, and virtualization in
> particular are not mature yet and need consistent investment
> of time and dollars to get RISC-V to the same level. That
> having been said I do see a lot of companies looking at it as
> a way to reduce their licensing costs. I think the motivation of
> the community should be to encourage corporate investment
> with the expectation that the resulting development is made
> available to everyone.
Reminds me of SEMATECH:
https://en.wikipedia.org/wiki/SEMATECH
/john
prev parent reply other threads:[~2021-12-01 21:36 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
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 [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/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='CAJnXXohK6AsnzTJCHK=SnYjQJ9L53Bg86hKL_R-pqg3NRp0sTQ@mail.gmail.com' \
--to=john@yates-sheets.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dpreed@deepplum.com \
--cc=ray@ramadorai.org \
/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