Timeline for How is virtual memory actually increasing the memory space?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2023 at 17:13 | comment | added | Krazy Glew | Less common, but important for some systems: PAE, as well as the style of virtual memory I call "address folding", e.g. Itanium and some IBM Power Processes can access more bits of virtual address by asking for the virtual to physical address mapping to be changed - mapping change only, not requiring I/O to disk or other swapping storage. They may do this repeatedly, so long as they don't need simultaneous mapping, and/or are willing to deal with data structures that can be remapped to different virtual addresses, e,g data structures that use offsets rather than absolute pointers. | |
| Nov 7, 2023 at 17:04 | comment | added | Krazy Glew | Virtual memory has frequently been used to increase physical memory. E.g. x86 PAE mode, Physical Address Extension, where the virtual address was 32 bits but the physical address larger. OS used PAE to allow more processes to reside in physical memory, avoiding page swapping overheads. | |
| Feb 8, 2017 at 14:21 | audit | First posts | |||
| Feb 8, 2017 at 14:21 | |||||
| S Jan 13, 2017 at 16:59 | history | mod moved comments to chat | |||
| S Jan 13, 2017 at 16:59 | comment | added | Sathyajith Bhat♦ | Comments are not for extended discussion; this conversation has been moved to chat. | |
| Jan 10, 2017 at 17:47 | history | edited | Mokubai♦ | CC BY-SA 3.0 |
added 736 characters in body
|
| Jan 10, 2017 at 17:32 | history | edited | Mokubai♦ | CC BY-SA 3.0 |
added 135 characters in body
|
| Jan 10, 2017 at 9:45 | history | edited | Mokubai♦ | CC BY-SA 3.0 |
edited body
|
| Jan 10, 2017 at 8:02 | history | edited | Mokubai♦ | CC BY-SA 3.0 |
added 214 characters in body
|
| Jan 10, 2017 at 7:56 | history | answered | Mokubai♦ | CC BY-SA 3.0 |