* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 23:02 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #21 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #19)
> (In reply to Luke Kenneth Casson Leighton from comment #17)
> > (In reply to Jacob Lifshay from comment #12)
> > > Assuming we're building a higher than 2W version, I think we should double
> > > the int/fpmul to 8x32-bit per core or maybe even quadruple it to 16x32-bit
> > > and add more cores to 8 or 16 or more cores.
> >
> > at 2.0 ghz this would start to put out some serious numbers :)
>
> I got 1TFLOP/s for 16 fma/clock/core with 16 cores, that's more than half
> the PS4's performance.
those are deeply impressive numbers :) the cross-over post explains however
that the number of RSes - and the data cache line widths etc. - are starting
to get rather scary.
48 LD/ST Reservation Stations would mean 96 160-bit PortInterfaces,
which is 15,360 wires coming into a single block!
we would be much better off going to 128-bit SIMD, which would have the
unfortunate side-effect of cutting scalar performance by another factor
of 2 in speed if there were register usage that could not be scheduled
correctly.
> > > Also, it might be worthwhile to add one more
> > > core and disable one at manufacture time as a way to increase yield.
> >
> > that's a good idea. have to bear in mind that current leakage occurs
> > regardless of whether the silicon is in use or not.
>
> If we set up each core as a different power domain (which will also help
> with idle power), the disabled core could be powered-down.
(you still get current leakage even when powered down, is my point)
> We should probably also widen the instruction decoders to decode 3 or 4
> 32-bit instructions per cycle.
yes. this will almost certainly be necessary, because we would have far more
instructions to keep the monstrous number of RSes "fed".
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 22:55 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #20 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #12)
> Assuming we're building a higher than 2W version, I think we should double
> the int/fpmul to 8x32-bit per core or maybe even quadruple it to 16x32-bit
> and add more cores to 8 or 16 or more cores.
ok. so expanding the number of cores is easy (less hassle) than expanding
the number Function Units (which directly correlates with the size of the
Dependency Matrices). so there is that in its favour.
the problem is that if you significantly increase the number of cores, SMP
coherency meets a point of diminishing returns unless you start doing very
advanced L1/L2 cache design and interconnect. so we had better take that
into consideration and budget and plan for it, appropriately.
using OpenPITON for example, this is a full "L1, L1.5, L2" write-through cache
strategy, which although it scales massively, might not provide good enough
localised performance.
basically if you double to 8x 32-bit per core, that means 4x 64-bit LD/ST
operations per clock cycle, because we would have 64-bit 2xFP32 SIMD units
(dynamic partitioning if we can do it, otherwise literally just 2x FP32
units).
the L0CacheBuffer will take care of amalgamating those into 128-bit cache-line
requests (cache line width to be evaluated, below).
4x 64-bit LD/ST operations, we will have out-of-order requests for at least
one pair of LDs and STs "in flight", simultaneously, therefore we need to
be able to hold *both* in the Reservation Stations, and preferably the
next set of LDs (at least), as well.
that's *twelve* LD/ST Computation Units.
that's *just* the LD/ST Computation Units - it does not include the
FP Computation Units as well. 4x 64-bit SIMD operations being processed,
let us assume those are FMACs, and assume a 4-stage pipeline, we would
need say 8 Reservation Stations because we want 4 in operation and another
4 "in-flight" to be held (so that we do not get a stall after processing
the previous ST).
- 4x LD in RS, being processed
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST in RS, waiting
- 4x LD in RS, waiting
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST stall (only 12 LD/ST RS's)
the next clock cycle, after the 1st LDs are complete:
- 4x LD done
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST in RS, waiting
- 4x LD in RS, waiting
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST now in RS, waiting (1st 4 LD/ST RS's were free)
so that's 20 Reservation Stations: 12 for LD/ST, 8 for FP.
let's go back to the 12x LD/ST operations. each would have 2x PortInterfaces:
one for aligned, one for misaligned. the L0CacheBuffer would therefore have
12 rows, 2 side-by-side odd/even addresses, receiving 24x PortInterfaces in
total.
each PortInterface would be around 160 wires wide (64 data, 64 addr, control)
that' 3840 wires into the L0CacheBuffer.
this is one hell of a lot of wires going into one small piece of silicon.
now let's see if 2x 128-bit L1 Caches are ok.
* 4x 64-bit requests will result in 2x 128-bit cache line requests.
* with 2x 128-bit Caches (one odd, one even), we are *just* ok
this as long as those requests can be made in a single cycle. this
does however mean that we need 4x 64-bit Wishbone Buses down to the
L2 Cache.
it also means that, because of the pass-through nature of GPU workloads
(data in, process, data out), we might need to sustain those 4x 64-bit
pathways *right* the way through to memory.
actually... no. this might not be enough. or, if it is, it's barely
enough.
we need the in-flight requests to be in-flight because they constitute
"advance notice" to the L1 and L2 caches. with the LDs and STs being
matched pairs, we *might* need just the one more LD set (20 LD/ST
RSes) and 1 more FP set (12 FP RSes) so as to be able to do this:
- 4x LD in RS, being processed
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST in RS, waiting
- 4x LD in RS, waiting
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST in RS, waiting
- 4x LD in RS, waiting
- 4x 64-bit SIMD FP32 in RS, waiting
- 4x ST stall (only 20 LD/ST RS's)
this would give us *advance notice* of the *next* set of 4x LD/ST,
which would do:
* Effective Address Computation (no problem)
* then the next phase push through to the L0CacheBuffer and
* pass through the requests to the L1 Cache and TLB and
* initiate a L2 Cache and L2 TLB lookup
whilst the request to memory might take a while to complete, at least
it would be outstanding, the reservation of the L1 Cache Line and
the L2 cache line would be made.
and for that to work, i think that 2x 128-bit cache lines isn't going
to cut it: we'd need 4.
so i think the L0CacheBuffer would need to do 2-bit striping:
* bits 4 and 5 == 0b00 Bank 0, L1 Cache number #1
* bits 4 and 5 == 0b01 Bank 1, L1 Cache number #2
* bits 4 and 5 == 0b10 Bank 2, L1 Cache number #3
* bits 4 and 5 == 0b11 Bank 3, L1 Cache number #4
this is basically monstrous.
for 16x 32-bit FP, i would not recommend going to 3-bit striping (8 L1
caches), i'd recommend expanding 4x L1 caches to 256-bit wide cache lines,
instead.
we would also need 48 LD/ST Reservation Stations, and 20 FP RSes.
that's starting to get a little scary. we could conceivably split
the Regfiles into odd-even numbering so that this number could be
halved.
whilst there would still be 48 LD/ST RSes and 20 FP RSes in total,
there would be 2 separate (square) Dependency Matrices @ (24+20) 40 wide.
honestly i would not recommend trying it, not without a much larger
budget.
even 8x FP32 is a little scary. those 40 RSes have to be joined by
Branch FUs, Condition Register FUs, predication FUs and so on.
which is why i said, it's probably much simpler to double the number
of SMP cores, instead.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 22:32 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #19 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #17)
> (In reply to Jacob Lifshay from comment #12)
> > Assuming we're building a higher than 2W version, I think we should double
> > the int/fpmul to 8x32-bit per core or maybe even quadruple it to 16x32-bit
> > and add more cores to 8 or 16 or more cores.
>
> at 2.0 ghz this would start to put out some serious numbers :)
I got 1TFLOP/s for 16 fma/clock/core with 16 cores, that's more than half the
PS4's performance.
> > Also, it might be worthwhile to add one more
> > core and disable one at manufacture time as a way to increase yield.
>
> that's a good idea. have to bear in mind that current leakage occurs
> regardless of whether the silicon is in use or not.
If we set up each core as a different power domain (which will also help with
idle power), the disabled core could be powered-down. We would probably want
each core to be it's own clock domain.
We should probably also widen the instruction decoders to decode 3 or 4 32-bit
instructions per cycle.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 22:19 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #18 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #14)
> (In reply to Jacob Lifshay from comment #13)
>
> > > this for the video framebuffer and the video framebuffer only.
> >
> > That doesn't really work, since the GPU will need lots of memory bandwidth
> > into the framebuffer since that's where it will be rendering to, potentially
> > drawing over the same pixels several dozen times. To support that, the
> > memory bandwidth of both the framebuffer and everything else needs to be
> > spread across all available memory interfaces.
>
> ok let's think it through, internally. would we have:
>
> * two separate memory interfaces, each dedicated to different address ranges
> * one L2 (L3?) cache, through which *both* memory interfaces have to go,
> first
> (note: the CPU/GPU as a Wishbone Slave, the RGBTTL HDL as a Master)
I think what would work the best is for the RGBTTL HDL and every core to be a
(extended) wishbone master to the L2 (L3?) cache, where the cache logic is the
arbiter and is designed to give the RGBTTL HDL highest priority and everything
else round robin (or other) priority. Saving power on scan-out when the data is
already in cache seems like a good idea, also, the memory interfaces would be
the tightest bottleneck, why require more accesses to go through them when that
can be avoided?
The memory interfaces would be organized into one larger super-interface where
each memory interface would be responsible for odd or even cache-block-sized
address blocks. The idea is that accessing something laid out contiguously in
physical address space would approximate balancing evenly across both memory
interfaces.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 22:05 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #17 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #12)
> Assuming we're building a higher than 2W version, I think we should double
> the int/fpmul to 8x32-bit per core or maybe even quadruple it to 16x32-bit
> and add more cores to 8 or 16 or more cores.
at 2.0 ghz this would start to put out some serious numbers :)
i'll do a walk-through separately so we are eyes-open on the layout and
wire count.
> The div and transcendental
> pipelines wouldn't probably need to be expanded since they would probably
> still have enough throughput.
the number of Function Units front-ends (aka "Reservation Stations") is
something we have to keep an eye on. above 30 FUs is pretty serious
size territory for the Dependency Matrices.
> Also, it might be worthwhile to add one more
> core and disable one at manufacture time as a way to increase yield.
that's a good idea. have to bear in mind that current leakage occurs
regardless of whether the silicon is in use or not.
> If possible, I think we should implement a cache-coherent memory interface
> over the PCIe bus so we can just have the host's linux kernel schedule
> processes as usual between the host POWER9 processor and the GPU, acting
> like the GPU is just more processor cores to schedule. That will allow nice
> things like using the GPU as extra CPU cores to help accelerate compile or
> other tasks and being able to use Kazan without needing lots of in-kernel
> GPU queues and stuff.
oo interesting.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 22:00 UTC (permalink / raw)
To: libre-riscv-dev
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 381] New: update algebraics for num-bigint v0.3
From: bugzilla-daemon @ 2020-06-12 21:53 UTC (permalink / raw)
To: libre-riscv-dev
https://bugs.libre-soc.org/show_bug.cgi?id=381
Bug ID: 381
Summary: update algebraics for num-bigint v0.3
Product: Libre-SOC's first SoC
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: ---
Component: Source Code
Assignee: programmerjake@gmail.com
Reporter: programmerjake@gmail.com
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
num-bigint v0.3 was just released, update algebraics to depend on the new
version.
This is an incompatible change so will update algebraics version to v0.3
https://crates.io/crates/num-bigint/0.3.0
https://salsa.debian.org/Kazan-team/algebraics
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 21:52 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #15 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
Yehowshua writes, "Some notes from my conversation with Michael":
>> from the ecp5 note on the serdes
>> - "3.2 Gbps operation with low 85
>> mW power per channel”
>
> Ok
> hmm
> channel i say 1rx or 1tx?
>
>> 1 tx/rx pair
>
>
> so 8 pairs at 3.2Gbps is about a watt
> Can't imagine for 25Gbps
>
>> Oh, and ecp5 is a 40nm chip
>> so it should be comparable to ours
>
>
> that’s what I’m afraid of
>
>
>> 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"
>
>> and I suspect ours will need to be less flexible than the ecp5's so that might save us some power
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 21:51 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #14 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #13)
> > this for the video framebuffer and the video framebuffer only.
>
> That doesn't really work, since the GPU will need lots of memory bandwidth
> into the framebuffer since that's where it will be rendering to, potentially
> drawing over the same pixels several dozen times. To support that, the
> memory bandwidth of both the framebuffer and everything else needs to be
> spread across all available memory interfaces.
ok let's think it through, internally. would we have:
* two separate memory interfaces, each dedicated to different address ranges
* one L2 (L3?) cache, through which *both* memory interfaces have to go, first
(note: the CPU/GPU as a Wishbone Slave, the RGBTTL HDL as a Master)
or would we have:
* two separate memory interfaces, each dedicated to different address ranges
* one L2 (L3?) cache, through which the CPU/GPU would read/write
(note: as a Wishbone Slave)
* the RGBTTL Wishbone Master would *bypass* the L2 cache and go directly
out to memory
if the L2 cache was write-through, then effectively i believe those are
the exact same thing? the advantage of the 2nd being that it cannot
interfere with or be distracted by any page faults or misses in the L2 cache.
(the RGBTTL interface *has* to - without fail - be able to feed its
SRAM buffer and meet its scanline timing - without fail. hence why
it is a Wishbone Master)
--
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
^ permalink raw reply
* Re: [libre-riscv-dev] Fall 2022 Interfaces
From: Luke Kenneth Casson Leighton @ 2020-06-12 21:42 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <D5B75159-31F2-4EA0-93F8-9382D6D6D64D@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Jun 12, 2020 at 8:34 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > no it really is 25GHz.
>
> Just talked with an engineer who has used the OpenCAPI
> SMC 100 from Microchip. It actually is 25GHz. 25.6 GHz to
> be precise.
makes sense, maps to 3200 gbytes/sec, which is the speeds you see for
things like the latest NVMe
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] [Bug 365] ROCM/Libre-SOC GPU Opcode interoperability
From: Luke Kenneth Casson Leighton @ 2020-06-12 21:40 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <bug-365-13-CoDR4t23oP@https.bugs.libre-soc.org/>
https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1185925-amd-publishes-video-to-explain-the-radeon-open-compute-stack-rocm?p=1185940#post1185940
:)
On Fri, Jun 12, 2020 at 7:24 PM <bugzilla-daemon@libre-soc.org> wrote:
>
> https://bugs.libre-soc.org/show_bug.cgi?id=365
>
> --- Comment #14 from Jacob Lifshay <programmerjake@gmail.com> ---
> https://www.phoronix.com/scan.php?page=news_item&px=AMD-Video-What-Is-ROCm
>
> --
> 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
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Fall 2022 Interfaces
From: Yehowshua @ 2020-06-12 19:43 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <D5B75159-31F2-4EA0-93F8-9382D6D6D64D@gatech.edu>
One of my Create-X mentors pointed me to
a U.S. organization that can allow us to prototype on 45nm
basically for free.
More on this later when details are finalized.
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] Fall 2022 Interfaces
From: Yehowshua @ 2020-06-12 19:34 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxge6pt4yx18nHY0Y6-f3rDOAF_Dq70YzbCqg8ud_DQCQ@mail.gmail.com>
>
> no it really is 25GHz.
Just talked with an engineer who has used the OpenCAPI
SMC 100 from Microchip. It actually is 25GHz. 25.6 GHz to
be precise.
Some notes from my conversation with Michael:
>> from the ecp5 note on the serdes
>> - "3.2 Gbps operation with low 85
>> mW power per channel”
>
> Ok
> hmm
> channel i say 1rx or 1tx?
>
>> 1 tx/rx pair
>
>
> so 8 pairs at 3.2Gbps is about a watt
> Can't imagine for 25Gbps
>
>> Oh, and ecp5 is a 40nm chip
>> so it should be comparable to ours
>
>
> that’s what I’m afraid of
>
>
>> 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"
>
>> and I suspect ours will need to be less flexible than the ecp5's so that might save us some power
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* [libre-riscv-dev] [Bug 365] ROCM/Libre-SOC GPU Opcode interoperability
From: bugzilla-daemon @ 2020-06-12 18:24 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-365-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=365
--- Comment #14 from Jacob Lifshay <programmerjake@gmail.com> ---
https://www.phoronix.com/scan.php?page=news_item&px=AMD-Video-What-Is-ROCm
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 18:13 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #13 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #11)
> (In reply to Jacob Lifshay from comment #7)
> > (In reply to Luke Kenneth Casson Leighton from comment #3)
> > > i am inclined to seriously recommend at least two separate OMI interfaces
> > > (with the option to use them in parallel), one to be connected to a video
> > > DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
> > > with the option to say "i don't care about that, just use one or both for
> > > general shared memory"
> >
> > I strongly disagree with the idea of partitioning memory interfaces between
> > GPU and CPU tasks,
>
> ah that is a misunderstanding, to clarify:
>
> > > arallel), one to be connected to a video
> > > DRAM chip,
>
> this for the video framebuffer and the video framebuffer only.
That doesn't really work, since the GPU will need lots of memory bandwidth into
the framebuffer since that's where it will be rendering to, potentially drawing
over the same pixels several dozen times. To support that, the memory bandwidth
of both the framebuffer and everything else needs to be spread across all
available memory interfaces.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 18:08 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #12 from Jacob Lifshay <programmerjake@gmail.com> ---
Assuming we're building a higher than 2W version, I think we should double the
int/fpmul to 8x32-bit per core or maybe even quadruple it to 16x32-bit and add
more cores to 8 or 16 or more cores. The div and transcendental pipelines
wouldn't probably need to be expanded since they would probably still have
enough throughput. Also, it might be worthwhile to add one more core and
disable one at manufacture time as a way to increase yield.
If possible, I think we should implement a cache-coherent memory interface over
the PCIe bus so we can just have the host's linux kernel schedule processes as
usual between the host POWER9 processor and the GPU, acting like the GPU is
just more processor cores to schedule. That will allow nice things like using
the GPU as extra CPU cores to help accelerate compile or other tasks and being
able to use Kazan without needing lots of in-kernel GPU queues and stuff.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 18:01 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #7)
> (In reply to Luke Kenneth Casson Leighton from comment #3)
> > i am inclined to seriously recommend at least two separate OMI interfaces
> > (with the option to use them in parallel), one to be connected to a video
> > DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
> > with the option to say "i don't care about that, just use one or both for
> > general shared memory"
>
> I strongly disagree with the idea of partitioning memory interfaces between
> GPU and CPU tasks,
ah that is a misunderstanding, to clarify:
> > arallel), one to be connected to a video
> > DRAM chip,
this for the video framebuffer and the video framebuffer only.
> > DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
this for the OS which in our case because it is a hybrid CPUVPUGPU
automatically and inherently includes CPU tasks, GPU tasks and VPU tasks.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 18:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #10 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Jacob Lifshay from comment #9)
> Additional note: Gigabit ethernet requires 4 tx and 4 rx serdes assuming we
> have the PHY integrated on-chip. All 4 twisted pairs are operated in both
> directions simultaneously.
>
> See section in https://en.wikipedia.org/wiki/Gigabit_Ethernet#1000BASE-T
>
> If we're integrating our own PHYs, it'd be nice to support 2.5G, 5G, and/or
> 10G as well.
Our own PHYs as in have Rudy and SymbyoticEDA design them, or actually doing
them ourselves? ... because from discussion of this from a few months ago it
seems like designing our own PHYs would be a 5+ year undertaking.
The higher speed ethernet interfaces will be very important for the higher
power consumption higher-end market segments. Good idea.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 17:56 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #16 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Alain D D Williams from comment #14)
> I will also point it at the latest version of buzilla that I installed a few
> days ago.
excellent.
> First thing is apache on port 8080, get that to work, then worry about
> proxying.
thats a good idea, just run open socket listen 8080:0.0.0.0 for now.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 17:44 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #9 from Jacob Lifshay <programmerjake@gmail.com> ---
Additional note: Gigabit ethernet requires 4 tx and 4 rx serdes assuming we
have the PHY integrated on-chip. All 4 twisted pairs are operated in both
directions simultaneously.
See section in https://en.wikipedia.org/wiki/Gigabit_Ethernet#1000BASE-T
If we're integrating our own PHYs, it'd be nice to support 2.5G, 5G, and/or 10G
as well.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 17:34 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
--- Comment #8 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Jacob Lifshay from comment #7)
> (In reply to Luke Kenneth Casson Leighton from comment #3)
> > i am inclined to seriously recommend at least two separate OMI interfaces
> > (with the option to use them in parallel), one to be connected to a video
> > DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
> > with the option to say "i don't care about that, just use one or both for
> > general shared memory"
>
> I strongly disagree with the idea of partitioning memory interfaces between
> GPU and CPU tasks, since the processors are designed to do both kinds of
> tasks well and splitting the memory interfaces up is basically saying: "all
> the CPU tasks can't use as much memory bandwidth as GPU tasks just because
> we say so". Also, I envision people building new varieties of tasks that are
> a hybrid between CPU and GPU tasks, so it will be harder to differentiate
> them because of things that fall in the grey areas.
I hadn't considered this. I think that this should be carefully discussed and
considered with someone who is an expert on data and on hardware
interconnects/buses. Rudy is one such person right?
I think the idea of new varieties of hybrid cpu-gpu algorithms is a very
interesting and compelling one. I'd be very interested in what ideas other
experts like those on comp.arch would have.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 376] Assess 40/45 nm 2022 target and interfaces
From: bugzilla-daemon @ 2020-06-12 17:26 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-376-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=376
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |programmerjake@gmail.com
--- Comment #7 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> i am inclined to seriously recommend at least two separate OMI interfaces
> (with the option to use them in parallel), one to be connected to a video
> DRAM chip, the other to be connected to a "OS / GPU" memory DRAM chip,
> with the option to say "i don't care about that, just use one or both for
> general shared memory"
I strongly disagree with the idea of partitioning memory interfaces between GPU
and CPU tasks, since the processors are designed to do both kinds of tasks well
and splitting the memory interfaces up is basically saying: "all the CPU tasks
can't use as much memory bandwidth as GPU tasks just because we say so". Also,
I envision people building new varieties of tasks that are a hybrid between CPU
and GPU tasks, so it will be harder to differentiate them because of things
that fall in the grey areas.
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
From: bugzilla-daemon @ 2020-06-12 17:15 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #15 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #12)
> (In reply to Luke Kenneth Casson Leighton from comment #11)
> > (In reply to Cole Poirier from comment #10)
> > > bugzilla product do discuss the specifics of these organizational matters.
> > > Can you please create a new component "Libre-SOC Organizational" for
> > > "Product: Libre-SOC's first SoC". Or would it be better to create a new
> > > bugzilla 'Product' "Libre-SOC Organization and Planning" like we have
> > > "Product Libre-riscv website"?
> >
> > yep. toplevel.
>
> done, default cc is libre-soc-org@libre-soc.org and you are the default
> assignee, congratulations.
Is it possible for me to be authorized to create 2nd level components to
supplement the "Planning" category? That is, access without needing to be
granted full access rights to the database and the whole administrative
apparatus of bugzilla?
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 379] Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 17:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-379-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=379
Cole Poirier <colepoirier@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |DUPLICATE
--- Comment #4 from Cole Poirier <colepoirier@gmail.com> ---
*** This bug has been marked as a duplicate of bug 380 ***
--
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
^ permalink raw reply
* [libre-riscv-dev] [Bug 379] Create wiki page for recruitment letter to Universities (& etc.) to point to
From: bugzilla-daemon @ 2020-06-12 17:09 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-379-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=379
Cole Poirier <colepoirier@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Cole Poirier <colepoirier@gmail.com> ---
Migrated to new toplevel "Libre-SOC Organization"
Bug 380 - First round of recruitment attempts on university and technical
mailing lists
<https://bugs.libre-soc.org/show_bug.cgi?id=380>
--
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
^ permalink raw reply
page: next prev latest
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