Thread (4 messages) flat view 4 messages, 3 authors, 2009-01-26

Re: [RFC PATCH] smsc911x: protect INT_EN read-modify-write with spinlock

From: David Miller <davem@davemloft.net>
Date: 2009-01-26 01:47:34

From: Steve Glendinning <redacted>
Date: Tue, 20 Jan 2009 14:01:54 +0000
This patch adds a new spinlock to protect read-modify-writes to the
INT_EN register when enabling and disabling interrupt sources.

I haven't actually seen any devices lock up, but I think there's a
possibility and I'd like to eliminate it.

Should I add this new spinlock, or should I extend the mac_lock
to also cover these sections (renaming it to simply "lock")?

Signed-off-by: Steve Glendinning <redacted>
If you didn't have all of these RX multicast workaround
cases, things would be much easier.

The POLL and normal interrupt paths are already completely atomic for
you already.  And since POLL cannot happen until open() completes
that path would be safe too.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help