Differences between version 2 and predecessor to the previous major change of VirtualMemory.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, March 9, 2004 10:02:19 pm | by StuartYeates | Revert |
| Older page: | version 1 | Last edited on Tuesday, February 25, 2003 1:27:02 am | by PerryLorier | Revert |
@@ -1 +1,3 @@
-The concept that the memory your program sees, is not the way memory is layed out physically. You may see memory with holes in it, or parts being read only, or execute only, and you probably don't see all of memory. This is
the idea of VirtualMemory
. See MemoryProtection
+The concept that the memory your program sees, is not the way memory is layed out physically. You may see memory with holes in it, or parts being read only, or execute only, and you probably don't see all of memory. This allows
the application to have memory with a consitent, logical layout and leave the OS to worry about implementing it
. On [Linux] it's quite possible for applications to use more memory than the machine has
[RAM], with parts not in active use being swapped to disk and other parts being mmap(2)'ed to conventional files as well.
+
+
See MemoryProtection MemoryMap
