Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 329] coriolis2 experiment layout for Dependency Matrices
Date: Wed, 03 Jun 2020 22:18:28 +0000
Message-ID: <bug-329-13-G8ef4V7ITL@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-329-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=329

--- Comment #10 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #9)
> (In reply to Luke Kenneth Casson Leighton from comment #8)
> > after a little thought, see the diagram in attachment "fu-fu matrix"
> > https://bugs.libre-soc.org/attachment.cgi?id=58
> 
> Hello Luke,
> 
> I'm starting to have automated matrix placement working for the FU-FU
> matrix.

superb.  do commit it, we can take a look.

> But the first comparison I can make between matrix placement
> and automated placement still got the later winning (by a little).

that's veery unlikely to be the case at 32x12, 32x25 or, when we go
to GPU DMs, 48x30 or even 128x30.   (this is FU-REGs, we are currently
investigating FU-FU, which will still potentially be be up to 30x30)


> I have two little remarks about the FU-FU example you gave me:
> 
> 1. It seems to me that the current example has 4 unit and 3 regs
>    (inverted in comment #5).

probably :)  actually for FU-FU it should be a square matrix.

> 2. Nothing is connected to gowr3_i, seems strange to me.

because if it's not a square matrix, that's what happens.

> I did try to generate a bigger FU-FU, but got stuck here:
> 
> Traceback (most recent call last):
>   File "fu_fu_matrix.py", line 169, in <module>
>     test_fu_fu_matrix()
>   File "fu_fu_matrix.py", line 166, in test_fu_fu_matrix
>     run_simulation(dut, d_matrix_sim(dut), vcd_name='test_fu_fu_matrix.vcd')
>   File "/usr/lib/python3.6/site-packages/nmigen/compat/sim/__init__.py",
> line 22, in run_simulation
>     fragment.domains += ClockDomain("sync")
> AttributeError: 'FUFUDepMatrix' object has no attribute 'domains'
> 
> I should have the latest nmigen, soc & nmutil repositry versions.

you need the version nmigen from whitequark, not from m-labs.
check the repo url in .git/config, it should be
https://github.com/nmigen/nmigen/

and you can ignore that, anyway - the ilang file-generation should
have happened before that.


> Would it be possible for you to generate a FU-FU matrix as close as possible
> to the one intended in terms of number of FU and registers (the idea is to
> have a representative amount of wires and gates).

let's make it 30x30 - that's pretty damn big.  for 180nm we'll likely go
with 1/2 that size.

> Best regards,
> 
> PS1: I use the approach of "not getting to the bottom of things but start
> like
>      a copying monkey", but always still felt a little bit like cheating.
> Now, I will
>      do it proudly...

haha very funny :)

> PS2: Maybe you have seen this... (personally, I'm at 110 characters)
>     
> https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Deprecates-
> 80-Col

sigh there's some severe problems with internet connectivity (much more
sophisticated than a DDOS attack), i still cannot get access to the
majority of news websites.  slashdot, theregister, phoronix, zoom, they're
all timing out (!)

if you can see this page https://slashdot.org/~lkcl then you'll see my
comments on this one.  summary: it's a serious mistake.  this screenshot
shows why: https://libre-soc.org/HDL_workflow/640x-2020-01-24_11-56.png

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 12:18 [libre-riscv-dev] [Bug 329] New: " bugzilla-daemon
2020-05-20 12:20 ` [libre-riscv-dev] [Bug 329] " bugzilla-daemon
2020-05-20 12:20 ` bugzilla-daemon
2020-05-20 12:30 ` bugzilla-daemon
2020-05-20 12:33 ` bugzilla-daemon
2020-05-20 12:33 ` bugzilla-daemon
2020-05-20 12:34 ` bugzilla-daemon
2020-05-20 12:41 ` bugzilla-daemon
2020-05-22 11:13 ` bugzilla-daemon
2020-05-22 13:35 ` bugzilla-daemon
2020-05-22 13:53 ` bugzilla-daemon
2020-06-03 22:00 ` bugzilla-daemon
2020-06-03 22:18 ` bugzilla-daemon [this message]
2020-06-06 10:41 ` bugzilla-daemon
2020-06-06 11:20 ` bugzilla-daemon
2020-06-06 11:23 ` bugzilla-daemon
2020-06-06 12:23 ` bugzilla-daemon
2020-06-06 12:25 ` bugzilla-daemon

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=bug-329-13-G8ef4V7ITL@https.bugs.libre-soc.org/ \
    --to=bugzilla-daemon@libre-soc.org \
    --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