one reason is the wafers that are good for storage (high gate capacitance) suck for computation, and vice versa
-
-
And this is why eDRAM isn't just "copy and paste a RAM design into the die".
1 reply 0 retweets 2 likes -
eDRAM?
2 replies 0 retweets 0 likes -
Intel's L4 cache / video RAM. Used on CPUs with Intel Iris graphics. Implemented on a second die sitting next to the CPU+GPU die itself.
1 reply 0 retweets 1 like -
Replying to @_sudoreality @sudoreality and
to add to this, eDRAM is the name of the concept (z/196 also uses eDRAM, for example), rather than Intel's impl
1 reply 0 retweets 2 likes -
Replying to @whitequark @sudoreality and
Intel's implementation isn't even "real" eDRAM (though by some definitions it qualifies). It's a separate die. I was talking about actually having eDRAM on the same die as logic. That's been common on game consoles since PS2/GameCube, and recently it's used for cache on POWER.
3 replies 0 retweets 3 likes -
Replying to @marcan42 @whitequark and
All that is still moving the data, with ever larger busses. I'm wondering if we can get away with not actually moving it, something like making DRAM refresh "smart" or "streaming".
1 reply 0 retweets 0 likes -
Replying to @dakami @whitequark and
The thing is DRAM doesn't spend a huge fraction of the time refreshing itself. DRAM is pipelined and you can stream data in/out of RAM pretty much as fast as the physical technology allows.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @whitequark and
Exactly! The streaming of data in and out _is the bottleneck_. So add compute when you are already processing the data anyway.
2 replies 0 retweets 0 likes -
Replying to @dakami @whitequark and
I'm not convinced you could put enough useful compute in RAM chips to be useful. Sure, streaming workloads would benefit, but those often involve big fat SIMD instructions. And then you have to deal with cache coherency.
1 reply 0 retweets 1 like
We're better off just making buses wider, which is what stuff like HBM does.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.