Adrian Bunk wrote:
> On Wed, Jul 18, 2007 at 08:55:50AM -0700, H. Peter Anvin wrote:
>> Andi Kleen wrote:
>>>> Already with these patches I can compile a zImage kernel that is 450kb
>>>> large (890kb decompressed)
>>> The important part is not how big the vmlinux is, but how much
>>> memory is actually used after boot.
>>>
>>> I expect concentrating some of the dynamic data structures would
>>> be more fruitful in fact.
>>>
>> Well, how big the vmlinux file is matters if it doesn't fit in memory
>> with enough time to get to the phase where it is dumping the init
>> sections. *If that is not the issue*, then axing stuff like CPUID is a
>> major lose in terms of code maintainability for zero gain.
>
> If this is an issue, then changing i386 back to discarding __exit code
> and data at linktime instead of runtime might make a bigger difference.
What would really make a big difference would be to unspool the
initramfs in such a way that it only requires O(1) instead off O(n)
extra memory, by freeing memory as it decompresses and decodes the cpio
ball.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
