[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-kernel
Subject: Re: 2.6.25-rc3: 34TB vmalloc total -- overflow in /proc/meminfo?
From: Andi Kleen <ak () suse ! de>
Date: 2008-03-06 11:30:38
Message-ID: 200803061230.38171.ak () suse ! de
[Download RAW message or body]
> but the first fundamental limit we'll hit on 64-bit is the 32-bit offset
31bit to be pedantic.
> limit of binaries - this affects kernel modules, the kernel image, etc.
If that ever happens just -fPIC mode would need to be supported
and a proper PLT for the references between modules and kernel. It would complicate
the module loader slightly, but not too much.
> We wont hit that anytime soon, but we'll eventually hit it. (user-space
> will be the first i guess)
I recently submitted a patch to fix the 2GB limit for user space
binaries (missing O_LARGEFILE). I think it made it into .25.
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.
Also of course you can always split the executable into ~2GB shared libraries.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic