Per Jessen wrote:
Timings for "make bzImage modules" (no other significant load):
HP xw6400 (four cores @ 2GHz, 2GB RAM, a 500Gb SATA drive). Timing: 43m49s (make -j4)
Intel SR1530AH (two cores @ 1.6GHz, 2GB RAM, 2 x 160Gb in RAID1 Timings: 134m18s (make -j2)
?!?!?! Why so long? 4.0 is a bit different from my normal scripted build: I type 'getlinuxrelease X.Y.Z', that downloads the patch to the previous mainline, creates a duplicate tree w/"cp -al", applies the patch then dups the new tree into a workspace. Usually it pulls the ".config" from the previous version, and does the standard "make oldconfig" -- I usually look through the config to see what's changed. 2 Intel Xeon chips at 1.60GHz - 2.80GHz w/6 cores each. "make -j16" takes about 3 minutes w/6 cores each. The config _is_ tailored to my machine, with modules needed for boot compiled into the kernel and over 500 "optional"/"loadable" modules. Wouldn't it be possible to modify something like Wicked to draw up a list of needed modules for a user's specific machine -- building in required HW (disks, file systems, etc) and making modules for "possible modules for your machine. After you have a list of your HW, for future builds, you can simply copy the previous config and do a "make oldconfig". I can't imagine kernel build times taking that long, but I don't compile modules for HW I don't have -- most of the modules are for software options. # modules per 'section':
du -s --inodes /lib/modules/3.19.3-Isht-Van/kernel/* 15 /lib/modules/3.19.3-Isht-Van/kernel/arch 24 /lib/modules/3.19.3-Isht-Van/kernel/crypto 288 /lib/modules/3.19.3-Isht-Van/kernel/drivers 44 /lib/modules/3.19.3-Isht-Van/kernel/fs 13 /lib/modules/3.19.3-Isht-Van/kernel/lib 278 /lib/modules/3.19.3-Isht-Van/kernel/net --- space:
du -sh /lib/modules/3.19.3-Isht-Van/kernel/* 11M /lib/modules/3.19.3-Isht-Van/kernel/arch 5.3M /lib/modules/3.19.3-Isht-Van/kernel/crypto 181M /lib/modules/3.19.3-Isht-Van/kernel/drivers 63M /lib/modules/3.19.3-Isht-Van/kernel/fs 3.2M /lib/modules/3.19.3-Isht-Van/kernel/lib 128M /lib/modules/3.19.3-Isht-Van/kernel/net
The time needed for "make modules" can be reduced significantly by amending the kernel configuration to suit your hardware. In my experience, getting an optimal config usually takes longer than building the kernel+modules :-)
?!? --- Once you've configued the kernel for your HW, you can reuse the prior-version ".config" with "make oldconfig" Given your build times, you might want to consider it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org