"Carlos E. R." <robin.listas@telefonica.net> writes:
The Thursday 2008-01-17 at 14:02 +0100, Roger Oberholtzer wrote:
The reason this came up was that I stopped worrying about supplying an -SMP version of a local device driver in our packages. Life was getting simple: only the -default kernel was needed. That didn't last so long. Now I need to dig up a system sunning a -BIGSMP kernel to compile the driver for the package. That's the hard part.
Notice that the default kernel is also an SMP kernel, so you may need to compile two versions: smp and bigsmp versions. There is no "no smp" version now.
I must be one of the few people on earth running a machine with a single, non smp, processor, so I usually recompile the kernel to suit. O:-)
You should not see any performance difference, the kernel figures out at runtime whether it's SMP or not and then uses the correct code. Check dmesg for something like: SMP alternatives: switching to UP code SMP alternatives: switching to SMP code Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126