5 ms·
It's interesting to see the shift in perspective. The first post was well in the "RISC era", several months before the P6 (PPro) came out and surprised everyone
by userbinator 5y ago
It's interesting to see the shift in perspective. The first post was well in the "RISC era", several months before the P6 (PPro) came out and surprised everyone. I would've loved to see what the engineers at Intel thought of this TLB discussion --- especially those who worked on the 386, and thus made the decision to go with a hardware TLB.
The idea of software-refilled TLBs always seemed strange to me; a TLB is a cache, yet I don't know of any widely-used CPU with data/instruction caches which need to be explicitly managed in software. ARM, the most common RISC now, uses a hardware TLB.
- johndoe0815 5y agoARM also provides software-managed high-speed memories, which the call Tightly Coupled Memory (TCM), the common term for these is scratchpad memory (SPM) [1]. There is still a lot of recent research focusing on the design of SPM hardware and management approaches in the embedded and real-time/predictable systems communities. [1] https://dl.acm.org/doi/10.1145/774789.774805 https://dl.acm.org/doi/10.1145/774789.774805
- throwawaylinux 5y agoTLBs do need to be explicitly managed by software, I don't know any CPU architecture where this is not the case. It would probably be quite feasible to do actually with an architecture that has a simple page table like a single physically contiguous hash table, but x86 style arbitrary radix page tables seem like they would be prohibitive to snoop.
- deleted 5y ago[deleted]
- cryptonector 5y agoIMO software-filled TLBs is the only thing that makes sense because it's much more flexible than any HW page table walking algorithms. The latter get baked in, or at best microcoded, while the former are infinitely customizable to fit the needs of the day. About the only improvement I can think of for software-filled TLBs is to have features that allow said software to always be hot, loaded into fast on-die memory, not subject to being pushed out of a cache.
- throwawaylinux 5y agoThe big problem of software filled TLBs is that taking an interrupt serializes the pipeline and is an inherently single-threaded operation. Interrupts themselves are very heavy weight on high performance cores too. You could handwave that way somewhat, but not the serial nature of it. Software filled just doesn't cut it for high performance cores. If an ISA defined a very small contained set of operations for TLB miss to program page table walking / TLB refill state machines that allowed the OS to define that behavior without taking an architectural interrupt that would be very cool. I suspect the hardware cost and complexity is not considered worthwhile though.