From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
Date: Fri, 12 Jun 2020 22:00:26 +0000
Message-ID: <bug-376-13-7sMXGCBBPg@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #16 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #15)
> > so 8 pairs at 3.2Gbps is about a watt
> > Can't imagine for 25Gbps
if we assume it's linear: 8x. 8 watts.
that's if it's linear. (if it's a square law, it's 64 watts.
i don't believe that to be the case).
chances are that it's linear, because the power consumption is
proportional to the amount of change that the signal has to be
dragged up and down.
consequently, we multiply the current draw by 8.
if however the speed of pullup/pulldown has to be *faster* than
it is carried out at 3.2ghz, then we're in trouble. it might
not be a square-law exactly but it would be close.
> > they might be targeting a different subprocess
> > than us though. I think most fabs offer the
> > options of like "low power", "high performance”,
> > or "high density"
this will be a dedicated analog block, extremely specialist,
with a full custom layout.
only when you have a digital layout do you have the option
of telling the yosys "synth" command:
* "please can you optimise for lower latency" (i don't care about power)
or
* "please can you optimise for gate reduction" (i don't care about latency)
these give you big and LITTLE respectively... but it's *only* something
you can do for digital layout.
--
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
next prev parent reply index
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 13:30 [libre-riscv-dev] [Bug 376] New: " bugzilla-daemon
2020-06-12 13:31 ` [libre-riscv-dev] [Bug 376] " bugzilla-daemon
2020-06-12 13:52 ` bugzilla-daemon
2020-06-12 15:14 ` bugzilla-daemon
2020-06-12 15:27 ` bugzilla-daemon
2020-06-12 16:17 ` bugzilla-daemon
2020-06-12 16:29 ` bugzilla-daemon
2020-06-12 17:26 ` bugzilla-daemon
2020-06-12 17:34 ` bugzilla-daemon
2020-06-12 17:44 ` bugzilla-daemon
2020-06-12 18:00 ` bugzilla-daemon
2020-06-12 18:01 ` bugzilla-daemon
2020-06-12 18:08 ` bugzilla-daemon
2020-06-12 18:13 ` bugzilla-daemon
2020-06-12 21:51 ` bugzilla-daemon
2020-06-12 21:52 ` bugzilla-daemon
2020-06-12 22:00 ` bugzilla-daemon [this message]
2020-06-12 22:05 ` bugzilla-daemon
2020-06-12 22:19 ` bugzilla-daemon
2020-06-12 22:32 ` bugzilla-daemon
2020-06-12 22:55 ` bugzilla-daemon
2020-06-12 23:02 ` bugzilla-daemon
2020-06-12 23:11 ` bugzilla-daemon
2020-06-12 23:14 ` bugzilla-daemon
2020-06-13 0:20 ` bugzilla-daemon
2020-06-14 5:06 ` [libre-riscv-dev] effects of powered-off chip sections on current leakage Jacob Lifshay
2020-06-14 11:30 ` Luke Kenneth Casson Leighton
2020-06-14 20:07 ` Jacob Lifshay
2020-06-14 22:08 ` Cesar Strauss
2020-06-13 3:37 ` [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces bugzilla-daemon
2020-06-14 17:27 ` 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-376-13-7sMXGCBBPg@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