On Mon, 5 Mar 2001, Jeff Garzik wrote:
> * spin_lock around your Tx interrupt handling path.
> * spin_lock_irq around your dev->hard_start_xmit Tx submission code.
>
> Ideally your Rx interrupt handling path is independent of other code,
> and need not be locked.
Well, if the Rx code modifies anything that is shared by all instances of
the Rx code (i.e. a queue or stack), you're going to need to lock around
those access points in order to be SMP safe. If the Rx code is in an
interrupt context, then you've got to spin_lock_irq.
--
Noah Romer |"Everyone is more or less mad on one point."
klevin@xxxxxxxxxx | - Rudyard Kipling
PGP key available |
by finger or email |
|