Re: Question on mmap() in 64-bit OS
- From: Josef Moellers <josef.moellers@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Nov 2007 10:41:33 +0100
LaBird wrote:
Hi Phil,
<phil-news-nospam@xxxxxxxx> wrote:
Come the day we actually need more than 48-bit addresses, there will also
be a lot of structural changes, primarily affecting the kernel and how it
handles things like virtual memory and simultaneous views of kernel space
and user space (things are a whole lot easier if the kernel can at least
have the whole kernel space and one whole VM in its view at once). Given
I agree with you. Perhaps with a large address space, the process space should be a global one for all processes in execution, rather than each process having its own process space.
You mean, that each process should be able to peek into another process' address space?
Think again: this is as non-secure as you can ever get.
--
These are my personal views and not those of Fujitsu Siemens Computers!
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://www.fujitsu-siemens.com/imprint.html
.
- Follow-Ups:
- Re: Question on mmap() in 64-bit OS
- From: phil-news-nospam
- Re: Question on mmap() in 64-bit OS
- References:
- Question on mmap() in 64-bit OS
- From: LaBird
- Re: Question on mmap() in 64-bit OS
- From: Wolfgang Draxinger
- Re: Question on mmap() in 64-bit OS
- From: LaBird
- Re: Question on mmap() in 64-bit OS
- From: phil-news-nospam
- Re: Question on mmap() in 64-bit OS
- From: LaBird
- Question on mmap() in 64-bit OS
- Prev by Date: Re: Question on mmap() in 64-bit OS
- Next by Date: Re: running Linux with no swap space (but lots of RAM)
- Previous by thread: Re: Question on mmap() in 64-bit OS
- Next by thread: Re: Question on mmap() in 64-bit OS
- Index(es):