Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] sun opensparc t2
Date: Fri, 1 May 2020 14:22:33 +0100
Message-ID: <CAPweEDxB5vW679Km54TzX7ofTL5evnCUz8WjVEWbN0mX15L08Q@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD4j4Ga=Z0n3b7QWMQ0C6FjxsZXHyeTt28H+G4=vJYuBEA@mail.gmail.com>

On Thu, Apr 30, 2020 at 11:50 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> the opensparc t2 is open source under the GPLv2, seems like it might be a
> useful reference.

really what we need, the immediate priorities are:

* the L0 cache/buffer
* a TLB (Radix) implementation to study (Paul Mackerras's microwatt
may be the first)
* a (long, important) discussion on how many ALU and LD/ST Comp Units to
  allocate, and how they should be connected to the register file(s).

these things stem from the requirements as a GPU/Hybrid OoO
multi-issue Vector-capable design with an augmented POWER front-end,
where we will run GNU/Linux OS workloads, and we're going for
single-core at the moment.  consequently there's unlikely to be much
we could use from it *right now*.

however looking at this:
http://fpga.ashishbanerjee.com/opensparc/t2-architecture

opensparc T2 apparently has some important characteristics which we
will need for the next version: L1 cache crossbar interconnect, and it
uses the opencores.org wishbone memory controller, which we should
definitely track down.

> it is a barrel processor, hence doesn't get very good single-threaded
> performance.

interesting...

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 22:50 Jacob Lifshay
2020-05-01 13:22 ` Luke Kenneth Casson Leighton [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPweEDxB5vW679Km54TzX7ofTL5evnCUz8WjVEWbN0mX15L08Q@mail.gmail.com \
    --to=lkcl@lkcl.net \
    --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