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] daily kan-ban update 22may2020
Date: Sat, 23 May 2020 13:08:02 +0100
Message-ID: <CAPweEDyXwLzu3dz=D9MCTznSf4_=jz8GevXUqnUVipVKmxuGBw@mail.gmail.com> (raw)
In-Reply-To: <6a1e761a-6e41-9431-647d-5e374b4d4134@gmail.com>

On Saturday, May 23, 2020, Cesar Strauss <cestrauss@gmail.com> wrote:

>
> Of course, I could use parts of libre-SOC, like the floating points
> pipelines. But, fixed-point algorithms are more common than
> floating-point in FPGA applications.


one of the big advantages of an OoO design is the opportunity for parallel
processing interwoven cleanly behind a sequential "API" (the instruction
set).

so let us suppose that you needed for example a significant number of fixed
point correlators, done in a specialist hardware-optimised mathematical way
that is massively inconvenient even for a DSP or a standard CPU.

however a full FPGA implementation is also inconvenient because the level
of parallelism required, when interacting closely with a sequential
program, makes the FPGA correlator a huge pain to program.

what you need would therefore be a CPU with sequential behaviour that could
just call a sequential instruction in a loop, to activate the special
custom correlator, but because that CPU is an out of order parallel
processor multiple such custom instructions (custom correlators) get issued
in parallel and the dependencies automatically resolved for you.

here you would get the best of both worlds.

another thought, for when we have time: if you can clearly express the
primitives needed, it would be a fascinating use-case evaluation to see
whether the ASIC would be any good, for the kind of DSP work that you do,
and if not, what operations would actually be needed.

l.





-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
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: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 15:02 Luke Kenneth Casson Leighton
2020-05-22 15:19 ` Michael Nolan
2020-05-22 15:39   ` Luke Kenneth Casson Leighton
2020-05-22 19:10 ` Cole Poirier
2020-05-22 19:18   ` Tobias Platen
2020-05-22 19:33     ` Luke Kenneth Casson Leighton
2020-05-23  1:56   ` Cesar Strauss
2020-05-23  2:41     ` Luke Kenneth Casson Leighton
2020-05-23 10:24       ` Cesar Strauss
2020-05-23 11:03         ` Luke Kenneth Casson Leighton
2020-05-23 11:53       ` Cesar Strauss
2020-05-23 12:08         ` Luke Kenneth Casson Leighton [this message]
2020-05-23 18:16     ` Cole Poirier
2020-05-22 19:59 ` Jacob Lifshay
2020-05-22 20:04   ` Luke Kenneth Casson Leighton
2020-05-22 20:12     ` 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='CAPweEDyXwLzu3dz=D9MCTznSf4_=jz8GevXUqnUVipVKmxuGBw@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