For a long time, the chip manufacturers had an inclination to simplify the hardware and rely on the software adapting and optimizing. But for decades this bid failed. Now we have the unrelenting AI capable of finetuning kernels relatively quickly. Maybe simpler hw will work this time? Note: not sure if TPU/NPU is not only simple but also too limited.
ahartmetz 22 hours ago [-]
I have some doubts. For example, there is no software replacement for out-of-order execution: It is unknown before runtime in which cache level the required data will be or which values it will have (which changes the latency of a few instructions).
Retr0id 22 hours ago [-]
What if caching was not transparent, but required explicit management?
frogblast 21 hours ago [-]
That was the PS3 SPU. It was very fast for its time, but only for the small subset of code that could work within its constraints, and viciously difficult to program for.
rasz 14 hours ago [-]
We tried that, doesnt work out in general computers running more than one task.
DSPs do that, Atari Jaguar, Sony PS2 and PS3 did, all the GPUs manually manage cache.
More than one task and you start a fight over resources, have to manage hierarchies, priorities, all the stuff that now happens automagically.
Can someone help me understand why I spent 5 minutes reading something that I still don't understand?
Link for the ELI5 version?
wmf 1 days ago [-]
There isn't really an ELI5 version of computer architecture but you could start with the book Inside the Machine by Jon Stokes. Then you can get into SIMT.
xyzsparetimexyz 1 days ago [-]
> Little of the detail of this path is documented by NVIDIA, at least not to the level that we’d like, so we’ll determine it by running timing experiments on the hardware itself
Or you could just use the AMD isa.
yipinwong 1 days ago [-]
This is a type of article that is HN worthy and came to HN for initially because I don't even understand a third of content there. Giving me inspiration to dive deeper.
SEriously, I don't understand it (yet) lol.
nazgulsenpai 1 days ago [-]
That's the best feeling -- idly clicking through looking for that one rabbit hole to fall down then stumbling upon a gem like this. I noticed this the first time on copetti.org articles about game console architectures: know nothing, look every jargon or acronym up as you read along, end up with 42 tabs and a basic high-level understanding of the topic by the end.
mathisfun123 1 days ago [-]
YMMV; not all GPUs work exactly like this
brcmthrowaway 1 days ago [-]
Ctrl+F PCIe BAR.. nothing.
porridgeraisin 1 days ago [-]
This is talking about HBM/GDDR
KK7NIL 1 days ago [-]
a.k.a. VRAM
brcmthrowaway 1 days ago [-]
Something needs to be transferred from sysmem right?
wmf 1 days ago [-]
That's probably PCIe DMA initiated by the GPU so I don't think BAR is used.
porridgeraisin 1 days ago [-]
Pcie dma uses BAR registers setup by cpu. It will contain information about the physical memory address for one. On newer systems, there is NVLINK C2C which is more tightly integrated and less general.
Regardless, my point was the the article is about vram.
However, there is one situation when vram access itself uses the bar, to be fair.
When you do P2P dma, code (kernel, either the inbuilt version or the one in the nvidia driver) running on the cpu sets up the DMA engines's GART to contain the BAR1s of the other.
Rendered at 22:34:03 GMT+0000 (Coordinated Universal Time) with Vercel.
DSPs do that, Atari Jaguar, Sony PS2 and PS3 did, all the GPUs manually manage cache.
More than one task and you start a fight over resources, have to manage hierarchies, priorities, all the stuff that now happens automagically.
"what every programmer should know about memory" https://github.com/Ty-Chen/Reading-List/blob/master/What%20e...
Here’s a clean version: https://people.freebsd.org/~lstewart/articles/cpumemory.pdf
Link for the ELI5 version?
Or you could just use the AMD isa.
SEriously, I don't understand it (yet) lol.
Regardless, my point was the the article is about vram.
However, there is one situation when vram access itself uses the bar, to be fair. When you do P2P dma, code (kernel, either the inbuilt version or the one in the nvidia driver) running on the cpu sets up the DMA engines's GART to contain the BAR1s of the other.