I'm running 2.6.0-test4 on my laptop, and it's quite nice. (Haven't beaten
also into submission yet, and it won't suspend, and kde is dropping some
events, but everything else is chugging along quite nicely...)
But the kernel is huge, an I'm curious why. So I did this in the build
directory:
find . -name "*.o" | xargs ls -l | less
And the results are interesting.
For example: I have a coppermine celeron in this laptop, and I told the build
that, and I did NOT select generic x86 optimizations, so why did it build
objects with names like amd, centaur, and cyrix, winchip, k7...?
-rw-r--r-- 1 root root 3348 Sep 1 01:24
./arch/i386/kernel/cpu/amd.o
-rw-r--r-- 1 root root 55962 Sep 1 01:24
./arch/i386/kernel/cpu/built-in.o
-rw-r--r-- 1 root root 2572 Sep 1 01:24
./arch/i386/kernel/cpu/centaur.o
-rw-r--r-- 1 root root 7908 Sep 1 01:24
./arch/i386/kernel/cpu/common.o
-rw-r--r-- 1 root root 5664 Sep 1 01:24
./arch/i386/kernel/cpu/cyrix.o
-rw-r--r-- 1 root root 4820 Sep 1 01:24
./arch/i386/kernel/cpu/intel.o
-rw-r--r-- 1 root root 7957 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/built-in.o
-rw-r--r-- 1 root root 2212 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/k7.o
-rw-r--r-- 1 root root 2184 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/mce.o
-rw-r--r-- 1 root root 2952 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/p4.o
-rw-r--r-- 1 root root 1600 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/p5.o
-rw-r--r-- 1 root root 2312 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/p6.o
-rw-r--r-- 1 root root 1264 Sep 1 01:24
./arch/i386/kernel/cpu/mcheck/winchip.o
-rw-r--r-- 1 root root 1452 Sep 1 01:24
./arch/i386/kernel/cpu/mtrr/amd.o
-rw-r--r-- 1 root root 23991 Sep 1 01:24
./arch/i386/kernel/cpu/mtrr/built-in.o
-rw-r--r-- 1 root root 3084 Sep 1 01:24
./arch/i386/kernel/cpu/mtrr/centaur.o
-rw-r--r-- 1 root root 3776 Sep 1 01:24
./arch/i386/kernel/cpu/mtrr/cyrix.o
Rob
On Mon, Sep 01, 2003 at 02:31:39AM -0400, Rob Landley wrote:
> I'm running 2.6.0-test4 on my laptop, and it's quite nice. (Haven't beaten
> also into submission yet, and it won't suspend, and kde is dropping some
> events, but everything else is chugging along quite nicely...)
>
> But the kernel is huge, an I'm curious why. So I did this in the build
> directory:
>
Yes, I have seen this too, but the kernel image size wasn't affected, only
the modules sizes.
I have posted a message on this recently, but nothing came from it... :(
Sorted by date:
7.7M Jul 14 15:03 ../kernel-image-2.6.0-test1_nmf.1_i386.deb
7.7M Jul 16 12:12 ../kernel-image-2.6.0-test1-drv-debug1_nmf.1_i386.deb
6.3M Jul 16 17:19 ../kernel-image-2.6.0-test1-mm1-06int_nmf.1_i386.deb
6.3M Jul 18 17:53 ../kernel-image-2.6.0-test1-mm1-07int_nmf.1_i386.deb
5.5M Jul 21 13:53 ../kernel-image-2.4.22-pre7_nmf.1_i386.deb
6.4M Jul 22 16:29 ../kernel-image-2.6.0-test1-mm2_nmf.1_i386.deb
6.3M Jul 25 11:36 ../kernel-image-2.6.0-test1-g2_nmf.1_i386.deb
6.4M Jul 28 19:00 ../kernel-image-2.6.0-test2-mm1_nmf.1_i386.deb
5.4M Aug 8 14:03 ../kernel-image-2.4.22-rc1_nmf.1_i386.deb
34M Aug 15 19:17 ../kernel-image-2.6.0-test3-mm2_nmf.1_i386.deb
34M Aug 24 15:43 ../kernel-image-2.6.0-test3-mm3_nmf.1_i386.deb
33M Aug 26 19:37 ../kernel-image-2.6.0-test4-mm1_nmf.1_i386.deb
33M Aug 29 13:54 ../kernel-image-2.6.0-test4-mm3-1-mdfail_nmf.1_i386.deb
33M Aug 30 19:39 ../kernel-image-2.6.0-test4-mm4_nmf.1_i386.deb