| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Reorganizing the address space
Reorganizing the address space
Posted Jul 1, 2004 15:14 UTC (Thu) by mwh (guest, #582)Parent article: Reorganizing the address space
I really thought the layout of the address space had more to do with /usr/lib/crt0.o and ELF
headers than the kernel. Am I hopelessly mistaken?
(Log in to post comments)
Reorganizing the address space
Posted Jul 1, 2004 20:28 UTC (Thu) by riel (subscriber, #3142) [Link]
When you call mmap(2) without specifying a preferred memory address, then the kernel's defaults kick in.Since moste mmap()s do not specify any address, the kernel's defaults determine the amount of contiguous virtual memory available to pretty much every application. This is what's fixed by Ingo's patch.
Effect of ELF headers on layout
Posted Jul 2, 2004 1:50 UTC (Fri) by giraffedata (subscriber, #1954) [Link]
While the ELF headers don't affect where the program's mmaps and mallocs get memory, they do determine where the program itself gets loaded. That means all the stuff that's in the ELF file - the text section, data section, etc.Note that the layout change here doesn't affect where the program gets loaded.