From: Yehowshua <yimmanuel3@gatech.edu>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Introduction and Questions
Date: Fri, 15 May 2020 15:33:51 -0400
Message-ID: <4BDA96A5-9063-42A6-9548-CAE3CBEBEBAC@gatech.edu> (raw)
In-Reply-To: <CAEoCstRUXkB_LxXXubx4A0dhLGvFqq6EPL+GzukDQORpHopaiw@mail.gmail.com>
> On May 15, 2020, at 3:15 PM, Jeremy Singher <thejsingher@gmail.com> wrote:
>
> Are you targeting IPC as the performance metric? Or IPC x Freq?
> The Pi 1 Rev B seems to be a 1-wide in-order design, so it should be a
> pretty conservative target to hit.
> Any basic OOO core should beat the PI B in IPC, it only needs to run
> at an equivalent frequency.
>
> Do you know what the final performance target is? (Or minimal target
> for a commercially viable product?)
> The Cortex A72 is a 3-w OOO that might be a good point to target (it's
> also used the latest Pi 4s).
>
> From running a couple experiments on other open-OOO cores, it seems
> like 3-ish DMIPs/MHz is a good
> target for a OOO core.
I know we initially were targeting 5GFLOPS for the GPU on the first tapeout.
Basically, the way we’re doing the GPU is the add a vector FPU along with
accompanying instructions into the actual CPU.
We would then just write the drivers that translate various shaders and drawing
commands into vector instructions which can be scheduled on the scoreboard.
Realistically, for our first tapeout(we’re using Google’s shuttle service on 1800nm TSMC),
we’d do a CPU with no vector instructions(effectively no GPU) for October.
Since we’re doing FOSS down to the VLSI design cells(we’re using Time Ansell’s OpenPDK as an intermediate), we need somebody to do a PLL.
With a FOSS PLL in place, we can get 300MHZ on the first tapeout. We’re doing a single core for the
first tape out, with 6 stages I think…
With no PLL, I think we’re limited to 25-50MHz.
Some simple math could give a DMIPS estimate.
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 18:24 Jeremy Singher
2020-05-15 18:45 ` Yehowshua
2020-05-15 19:15 ` Jeremy Singher
2020-05-15 19:20 ` Yehowshua
2020-05-15 19:24 ` Yehowshua
2020-05-15 19:33 ` Yehowshua [this message]
2020-05-15 20:11 ` Luke Kenneth Casson Leighton
2020-05-15 20:50 ` Jeremy Singher
2020-05-15 21:03 ` Yehowshua
2020-05-15 21:19 ` Jacob Lifshay
2020-05-15 21:55 ` Luke Kenneth Casson Leighton
2020-05-15 21:53 ` Luke Kenneth Casson Leighton
2020-05-15 22:15 ` Jeremy Singher
2020-05-15 22:29 ` Yehowshua
2020-05-15 22:51 ` Luke Kenneth Casson Leighton
2020-05-15 22:47 ` Luke Kenneth Casson Leighton
2020-05-15 23:49 ` Jeremy Singher
2020-05-16 0:40 ` Luke Kenneth Casson Leighton
2020-05-16 9:47 ` Staf Verhaegen
2020-05-16 11:30 ` Staf Verhaegen
2020-05-16 12:30 ` Luke Kenneth Casson Leighton
2020-05-16 20:34 ` Jeremy Singher
2020-05-16 21:42 ` Luke Kenneth Casson Leighton
2020-05-16 9:43 ` Staf Verhaegen
2020-05-16 12:14 ` Luke Kenneth Casson Leighton
2020-05-15 18:47 ` Yehowshua
2020-05-16 12:11 ` Luke Kenneth Casson Leighton
-- strict thread matches above, loose matches on Subject: below --
2020-05-15 6:50 Jeremy Singher
2020-06-06 22:47 ` Yehowshua
2020-06-06 22:48 ` Luke Kenneth Casson Leighton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BDA96A5-9063-42A6-9548-CAE3CBEBEBAC@gatech.edu \
--to=yimmanuel3@gatech.edu \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git