Page 1 of 1

Speeding and tweeking the kernel

Posted: Tue Sep 13, 2005 3:44 pm
by CptnObvious999
Hey I just got the newest kernel and installed it (yet still trying to get it to work). I was wondering if I could edit the config files for one kernel so the hardware I don't have wont load (eg. RANDOM_DRIVER=m could be changed to RANDOM_DRIVER=n) would it make it faster to startup? Also give me any other kernel tweeking trick you might have. And how do I make the startup output less cryptic (so it looks like the pretty one from Gentoo)? Maybe this could be a discussion for an upcoming show. Just a suggestion :wink:

Posted: Wed Sep 14, 2005 2:14 pm
by dann
There are three options for modules: Compiled into the kernel, compiled as a module or not compiled at all. The debate as to whether there is a boost in system performance if a module is compiled into the kernel or as a modules has pretty much been put to rest with newer system indicating that there is really no discernable impact on speed. Generally speaking, most distributions target the widest array of hardware by compiling modules sperate from the kernel. This allows for a smaller kernel that can be applied to the widest array of hardware.

I don't think you will see any speed performance during the boot process if a driver is compiled into the kernel or not. Or more to the point, any speed boost would be pretty much neglible.

If a driver is compiled into the kernel it will not be activated if you do not have the hardware. Thus, you will not be experiencing any speed issues with regards to unused drivers. Your kernel will, though, obviously take up more space.

So to answer your question, though, I doubt you will see a speed performance by not including a driver as a module for hardware that does not exist.

Also, by editing the config files, I hope you don't mean by hand. You should use the utilities like make config, menuconfig, oldconfig, etc. When you enable/disable a driver the change can effect more than one setting in the config file and thus, changing a driver by had in .config may not make all the necessary changes that must take place.

One thing you can do to help speed up hardware detection with regards to hotplug would be to put the modules you know you will not be using in the blacklist file. How much this may help speed up the boot process I do not know and quite honestly, it may not make much of a difference at all.

Secondly, turn off any services you are not using. For instance, if you are just running a workstation chances are you do not need apache, mysql, rpc, ntp, bind, etc. Getting rid of those services at startup will help speed things along.

Posted: Wed Sep 14, 2005 2:41 pm
by CptnObvious999
Ok thanks. Is there anyway to make the output cleaner? Can I use a quiet flag to show only if it failed or succeded? I tryied to get bootsplash to install but it doesn't seem to like newer kernels or something. I want to get this system very custom tuned so its very sleek :wink:

Posted: Wed Sep 14, 2005 9:09 pm
by Ridgid
I do not know if this will help you do what you want. nor have looked at this in great detail as it is a little over my head. (I bookmarked it a few weeks ago) hence how good the info is I do not know. maybe there will be some usefull info in there for you.

http://www.improvedsource.com/view.php/Linux-System/2/

Ridgid