Re:Lots of bugs in 32-bit x86 Linux entry code
by eru on Friday December 13, 2019 @12:50AM
(#21779396)
Exactly, you probably won't.
And I don't mean that in an absolute sense. People might very well get up to those orders of magnitude of RAM; but you are unlikely to have that amount of RAM available to a single processor.
The extra margin of the 64 bit might help with address space randomization, though.
Re:Lots of bugs in 32-bit x86 Linux entry code
by jagger27 on Friday December 13, 2019 @04:55AM
(#21780369)
Memory banking is the obvious and ancient solution. PAE is another.
Re:Lots of bugs in 32-bit x86 Linux entry code
by amluto on Friday December 13, 2019 @12:12PM
(#21783367)
PAE is a kludge because the architects needed to add another tiny page table level to keep 32 bits of virtual space, but didn’t really want to add another level.
The concept of having more physical address bits than virtual bits is reasonable, although it falls apart a bit with virtualization. The idea of having magic registers that fill themselves in for you and can’t be read at all (such as the PAE PDPTR registers) is a bad idea that unfortunately repeats itself in x86 design. Architects: don’t do this.
How else are you going to have more than 16 exabytes of RAM?