On Sun, Apr 02, 2000 at 04:05:01PM -0700, Matthew Dharm wrote:
> Correctly, as Vojtech points out, it's
> improper for me to hold the _irqsave spinlock. Tho, oddly enough, it
> seems to work for me on my system. But Vojtech is correct, and I will fix
> this tomorrow morning.
That's because, if I recall correctly, on a single processor system a
spin_lock is a nop and spin_lock_irqsave is just cli(), so while your
spinlocking doesn't break anything, it also doesn't help.
By the way, keep in mind that even kmalloc, if not allocating atomic
memory can schedule() as well.
--
Vojtech Pavlik
SuSE Labs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
