Messages in this thread | | | Date | Thu, 6 Mar 2008 22:06:52 +0100 | From | Ingo Molnar <> | Subject | Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo? |
| |
* Andi Kleen <ak@suse.de> wrote:
> > but the first fundamental limit we'll hit on 64-bit is the 32-bit > > offset > > 31bit to be pedantic.
yeah.
> [...] > > Newer gcc/binutils support the large code model so you could actually > try to generate binaries that big :-) e.g. some of the rtl-to-C > compilers seem to generate huge code so it might be actually useful.
The largest kernel image i've had so far was slightly above 40MB so at least in the kernel we are not there yet ;-)
Do you have any experience with how much of a size difference there is when binaries are built for big address mode? I'd expect something in the neighborhood of 5% for an image with a structure similar to the kernel's but maybe it's more.
> Also of course you can always split the executable into ~2GB shared > libraries.
... which brings back happy memories of DOS extenders ;-)
Ingo
| |