Messages in this thread | | | From | (Alan Cox) | Subject | Re: CONFIG_SMP patch available for 2.1.54 | Date | Tue, 9 Sep 1997 22:08:48 +0100 (BST) |
| |
> Mine does. I have an IBM SLC/486-33. Uniprocessor 2.1.54 works fine, > but SMP 2.1.54 gives me an unlimited number of "lock from interrupt > context at %p\n" messages. I don't mind because I don't expect 486 SMP > to work anyways. (But this did prevent me from testing my CONFIG_SMP > patch very well).
What drivers. There is no reason for the problem you are seeing being a CPU specific bug - its most likely a driver flaw. What drivers do you use and does 2.0.x SMP work for your box
> Personally I would like to get rid of about half these tests and just go > with the fractionally slower code with no configuration tests. I don't > mind having arch/i386/kernel/smp.c linked in or not depending on __SMP__, > but I don't like seeing __SMP__ in the middle of low-level include files. > Besides the code cleanup benefit, it would eliminate the distinction > between SMP and non-SMP modules.
The difference on intel for non SMP with things like FPU heavy tasks can be over 100% gain. Its worth having SMP seperate.
Alan
| |