Re: Have the 2.4 kernel memory management problems on large machines been fixed?

[Martin J. Bligh]

>> The solution really is a "don't do it then" kind of thing. If you have 
>> 5000 processes that all want to map a big shared memory area, and you 
>> don't want to upgrade your CPU's, it's a _whole_ lot easier to just have a 
>> magic "map_large_page()" system call, and start using the 2MB page support 
>> of the x86.
> 
> map_large_page() sounds decent, though I don't really know how easy
> it'll be to get apps to cooperate. I suspect it's easier when the
> answer is "the app crashed" as opposed to "the kernel crashed".

If we could get the apps (well, Oracle) to co-operate, we could just use
clone ;-) Having this transparent for shmem segments would be really nice.

M.