patch-2.1.99 linux/Documentation/spinlocks.txt
Next file: linux/Documentation/stallion.txt
Previous file: linux/Documentation/specialix.txt
Back to the patch index
Back to the overall index
- Lines: 18
- Date:
Tue Apr 28 14:22:05 1998
- Orig file:
v2.1.98/linux/Documentation/spinlocks.txt
- Orig date:
Mon Jan 12 14:46:16 1998
diff -u --recursive --new-file v2.1.98/linux/Documentation/spinlocks.txt linux/Documentation/spinlocks.txt
@@ -6,7 +6,7 @@
> SMP safe as well as UP safe during interrupts and other manipulating
> routines. So far, I've added a spin_lock variable to things like my queue
> structs. Now, from what I recall, there are some spin lock functions I can
-> use to lock these spin locks frmo other use as oppossed to a (nasty)
+> use to lock these spin locks from other use as opposed to a (nasty)
> save_flags(); cli(); stuff; restore_flags(); construct. Where do I find
> these routines and go about making use of them? Do they only lock on a
> per-processor basis or can they also lock say an interrupt routine from
@@ -25,7 +25,7 @@
... critical section here ..
spin_unlock_irqrestore(&xxx_lock, flags);
-and the above is always safe. It will disable interrupt _locally_, but the
+and the above is always safe. It will disable interrupts _locally_, but the
spinlock itself will guarantee the global lock, so it will guarantee that
there is only one thread-of-control within the region(s) protected by that
lock.
FUNET's LINUX-ADM group, linux-adm@nic.funet.fi
TCL-scripts by Sam Shen, slshen@lbl.gov