Timeline for Memory limits in 16, 32 and 64 bit systems
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:41 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jul 9, 2015 at 11:24 | history | edited | 0xC0000022L | CC BY-SA 3.0 |
added 98 characters in body
|
| Aug 9, 2014 at 0:58 | comment | added | 0xC0000022L | @JamieHanrahan: ... at least two on newer systems (due to virtualization), which opens up some exciting possibilities. His (Linus') comparisons aren't completely right, but if it's a foreign concept, metaphors can help :) ... I guess that was why he chose it to make his point. | |
| Aug 8, 2014 at 21:21 | comment | added | Jamie Hanrahan | Linus's comments are strange. There is no relationship between how himem.sys works and how PAE works. It is very amusing to see people argue for x64 and against PAE addressing... when x64 long mode simply takes the PAE scheme and adds one more level of page table! | |
| May 6, 2014 at 17:27 | comment | added | supercat | I understand that PAE would be a nuisance for any code which needed more than a couple gigs of working set, and for system-level code that needs to manage multiple tasks of 2 gigs or so each, but unless a single application needs more than 2 gigs I would expect PAE to be transparent. Further, I would think PAE would also be better than global use of 64-bit pointers in cases which needed 3 gigs of general-purpose RAM plus a large disk cache or temp-storage drive. | |
| Feb 24, 2013 at 2:02 | comment | added | Karan | Hmm, why do I get the impression that Linus really hates HIGHMEM.SYS and PAE? :P | |
| Feb 22, 2013 at 22:18 | history | answered | 0xC0000022L | CC BY-SA 3.0 |