kernel compile ?'s
 

I want to try and get the fastest kernel possible.

Better to build a module or to build it into the kernle?? Building it in adds more to the kernel but does using something as a module slow in down??

Also, does just have a bunch of modules sitting around slow the kernel down?? Like on the stock kernel there is ALOT of modules made, although i am only using a few so are the ones i am not using slowing the kernel down?

thanks

Modules you use all he time may be build into the kernel. Those you use from time to time - as modules. In fact, there's no big difference between a build in kernel driver and module (when loaded). The difference is when you load/unload modules (it takes some time).

If you'd like to have fast kernel, don't forget to compile it for you processor...

Only in terms of your default startup-scripts
trying to load them :)

And as some are loaded, they take up a few
micro-/milliseconds. The ones you don't actually
don't load don't do anything if you weed through
your /etc/rc.d/rc.modules and comment out things
you don't have/need.

The major difference between module and built-in
is the load time during boot-up. Once in memory
you shouldn't be able to tell the difference. :)

Cheers,
Tink

Ok thanks....

hey tinkster, does your geek code block translate into something?

Actually, yes :)

Look at my public bookmarks :} to find out... ;)


Cheers,
Tink

Cool, at first I was like no way, those symbols cant say all that....then after further reading I see that they are just abbreviations for phrases.

There are two choices for what kind of kernel you'll recompile....a MODULAR kernel(one with modules enabled) and the other is the MONOLITHIC kernel(no modules can be installed)

Then there's an issue of whether you're booting from a floppy...in which case you have to limit the features in order have less than 955 kilobytes....

When choosing the features....choose only what you'll be using everyday....if you don't support multi-processors or USB, then you can remove support so the bzImage is smaller...


1)for modular build
make menuconfig
make dep
make bzImage
make modules
make modules_install
mkinitrd -f -v /boot/initrd-2.4.18-trial1.img 2.4-trial1 (this varies)
edit GRUB or LILO then reboot


2)for monolithic build
make menuconfig
make dep
make bzImage
edit GRUB or LILO then reboot

To comment what dfbreyes wrote I'd like to add that in 99.9% kernel builds modular approach is used. Monolithic kernels are just too big. And it's much easier to add a new NIC module for modular kernel (just make xconfig;make modules;make modules_install). Monolithic kernel is good for example for a boot (rescue) floppy, designed especially for your system.