Re: Process address space

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "Marvin" == Marvin Justice <mjustice@austin.rr.com> writes:
Marvin> x86). A nice description of how the address space is layed out along with a 
Marvin> discussion of malloc's limitations can be found in the lkml archives for July:

Marvin> http://www.uwsg.indiana.edu/hypermail/linux/kernel/0107.1/0193.html

FUD or just plain stupid. He could have solved all the problems he
described by just simply linking statically his proggie.

> Anyway, I just wanted to let you know that there are some glibc issues that
> are more restrictive than the kernel issues.

FUD. Period. On my system mozilla's (as an example of shlib heavy app)
shared libraries occupy (with holes) 0x40000000-0x417bc000 ==
0x17bc000 == 24887296 ~= 23.7 MB. What's the problem allocating
libraries at e.g. 0x8000000? Or 0xa0000000?
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux