Why is kernel restricted to use virtual addresses of only 1 GB? Or
what is the need to split up the virtual address space into user
addresses and kernel addresses?
We can have 4GB for kernel and 4GB for userspace but this has a overhead
of flushing of tlb for every syscall.
You can also make
Also, go through the following article, they have explained things in
a very nice way.
http://kerneltrap.org/node/2450
On 3/21/07, Vivek [EMAIL PROTECTED] wrote:
Why is kernel restricted to use virtual addresses of only 1 GB? Or
what is the need to split up the virtual address space into
3/21/07, Vivek [EMAIL PROTECTED] wrote:
Why is kernel restricted to use virtual addresses of only 1 GB? Or
what is the need to split up the virtual address space into user
addresses and kernel addresses?
We can have 4GB for kernel and 4GB for userspace but this has a overhead
of flushing of
On 3/22/07, Prasad Joshi [EMAIL PROTECTED] wrote:
3/21/07, Vivek [EMAIL PROTECTED] wrote:
Why is kernel restricted to use virtual addresses of only 1 GB? Or
what is the need to split up the virtual address space into user
addresses and kernel addresses?
We can have 4GB for kernel and
Hi,
Why is kernel restricted to use virtual addresses of only 1 GB? Or
what is the need to split up the virtual address space into user
addresses and kernel addresses?
TIA,
Rick
-
To unsubscribe from this list: send the line unsubscribe linux-newbie in
the body of a message to [EMAIL
