SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am looking to safely trim more options out of the 2.6.27-generic-smp kernel. I use Slackware mainly for desktop/multimedia purposes on very modern hardware, so I am sure there are some legacy and server slanted type options that go into the kernel of stuff that I will never need.
The only changes I make are:
Under processors and features:
-Change kernel to preemptive
-Set timer frequency to 1000Hz
-Compile for Core 2 arch
I would enable "paravirtualization guest support" if it's not yet (I do not remember). There are a lot of modules you can disable under "Device drivers" but this will take you a lot of time and won't get things any faster. Would you do that though be careful not to remove anything you need. At least check lspci -k and also lsmod to make sure.
Last edited by Didier Spaier; 03-31-2009 at 06:22 AM.
Removing unneeded modules takes a lot of time but if you frequently compile kernels, it will make future compilations faster, so I'd say it would be worth the effort. It's a good idea to check lsmod output to see what modules are needed. Of course, you should know your hardware and leave the relevant kernel options enabled.
Some of the things that I change (in addition to what you listed):
- Drop unneeded modules and hardware support (like I have no AGP slots on my laptop motherboard, no floppies, tape drivers, etc.).
- Enable dynamic ticks
- I compile (some of) the modules always needed into the kernel (ext3, sata, cryptography etc).
- I have a single core CPU so I disable the SMP option.
- Make the ondemand governor the default
- Disable some debugging feautres (usually under the General and Small Systems sections)
Distribution: Slint64-14.2beta3 on Lenovo Thinkpad W520
IMHO disable SMP option is useless. I have a single core CPU and I noticed that the kernel is smart enough to check that and act accordingly. An extract of dmesg's output follows (customized 2.6.29-smp but I get similar output with Slackware's -smp kernels):
[ 0.004295] Intel machine check architecture supported.
[ 0.004308] Intel machine check reporting enabled on CPU#0.
[ 0.004328] Checking 'hlt' instruction... OK.
[ 0.020377] SMP alternatives: switching to UP code
Anyway _it's_your_choice_ but if you choose to do so read the warning in CHANGES_AND_HINTS.TXT
PS Time is in seconds. You can see that the kernel needs less than 2/100 second to think about that
Last edited by Didier Spaier; 03-31-2009 at 11:02 AM.
I'm aware of that. The kernel detects the number of cores at runtime and adjusts itself. Still, compiling for single core would save me from some if() statements, so why not do it, if it doesn't break anything?