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.
Pat V. recommends using the SMP kernel even on single core CPUs. Is that a good idea on really old CPUs?
I want to update my old box to Slackware 12.1. Currently on that box is Slackware 12.0 with a recompiled 188.8.131.52 non-SMP kernel.
I don't want to (and can't) use my kernel configuration file for my new box. That box is a dual core AM2 BE-2400 (K8) with 4 GB of RAM. I also have more hardware on the new box that is not available on the old box. I don't even run udev on the old box because the hardware is static and I don't use USB there.
My old box runs a 400 MHz K6-III+ with 256 MB of RAM. So even if the recommendation remains to use the SMP kernel, I need to modify the configuration down to that level.
Typically I would update the config file by running make oldconfig. I'm still inclined to continue that habit unless somebody explains in a compelling manner why I should switch to the SMP kernel for this old box.
If you want to use a recent kernel, its hard to do anything else.
The argument from the kernel developers is that, these days, the performance hit of using an smp capable kernel on a non-smp cpu is so low, why should they support anything else? So, where you once had to get a kernel with 'smp' in the name to get smp support, nowadays the default kernel is smp (but doesn't have smp in the name) unless someone downstream has hacked it to take out the smp capabilities.
I've been trying to investigate when exactly this happened, and the closest I can come up with is this comment:
So, where you once had to get a kernel with 'smp' in the name to get smp support, nowadays the default kernel is smp (but doesn't have smp in the name) unless someone downstream has hacked it to take out the smp capabilities.
Um...I don't think any hacking is needed, unless the kernel is really really screwy. There is a CONFIG_SMP option -- the help states this:
│ CONFIG_SMP: │
│ This enables support for systems with more than one CPU. If you have │
│ a system with only one CPU, like most personal computers, say N. If │
│ you have a system with more than one CPU, say Y. │
│ If you say N here, the kernel will run on single and multiprocessor │
│ machines, but will use only one CPU of a multiprocessor machine. If │
│ you say Y here, the kernel will run on many, but not all, │
│ singleprocessor machines. On a singleprocessor machine, the kernel │
│ will run faster if you say N here. │
│ Note that if you say Y here and choose architecture "586" or │
│ "Pentium" under "Processor family", the kernel will not work on 486 │
│ architectures. Similarly, multiprocessor kernels for the "PPro" │
│ architecture may not work on all Pentium based boards. │
│ People using multiprocessor machines who say Y here should also say │
│ Y to "Enhanced Real Time Clock Support", below. The "Advanced Power │
│ Management" code will be disabled if you say Y here. │
│ See also the <file:Documentation/smp.txt>, │
│ <file:Documentation/i386/IO-APIC.txt>, │
│ <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at │
│ <http://www.tldp.org/docs.html#howto>. │
│ If you don't know what to do here, say N. │
│ Symbol: SMP [=y] │
│ Prompt: Symmetric multi-processing support │
│ Defined at arch/x86/Kconfig:174 │
│ Location: │
│ -> Processor type and features │
│ Selected by: X86_VOYAGER && <choice> && X86_32 && !BROKEN || X86_NUMA │
The CONFIG_SMP option is not set in the generic or huge non-smp kernels.