Comment Re:Clarification (Score 2) 150
You are completely wrong with this.
The issue is not to enlarge the virtual address space of a process, but to enlarge the total probable physical memory to the kernel. The processes still do see only 3GB of virtual memory.
The difference is, that previously all physical memory had to be mapped into the kernel virtual address space (hence max. 3GB and then 1GB virtual memory to processes), now this is no longer true. Now we have two sorts of memory, normal memory that is always mapped into the kernel virtual address space and the high memory (all above 3GB but to have 3GB virtual address space to processes its usually all above 1GB) which is mapped on-demand to a special virtual address range in the kernel (which is also the overhead of this model).
Richard.
The issue is not to enlarge the virtual address space of a process, but to enlarge the total probable physical memory to the kernel. The processes still do see only 3GB of virtual memory.
The difference is, that previously all physical memory had to be mapped into the kernel virtual address space (hence max. 3GB and then 1GB virtual memory to processes), now this is no longer true. Now we have two sorts of memory, normal memory that is always mapped into the kernel virtual address space and the high memory (all above 3GB but to have 3GB virtual address space to processes its usually all above 1GB) which is mapped on-demand to a special virtual address range in the kernel (which is also the overhead of this model).
Richard.
