| To: | Mark Broadbent <markb@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] Tulip interrupt uses non IRQ safe spinlock |
| From: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 3 May 2005 07:28:19 +1000 |
| Cc: | Sergey Vlasov <vsu@xxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <4276238E.4060606@xxxxxxxxxxxxxx> |
| References: | <E1DRFqC-00028H-Qi@tigger> <E1DRGWv-0003aa-00@xxxxxxxxxxxxxxxxxxxxxxxx> <20050429093521.274adf9a.davem@xxxxxxxxxxxxx> <20050429214336.04b40b3f.vsu@xxxxxxxxxxx> <4276238E.4060606@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.6+20040907i |
On Mon, May 02, 2005 at 01:56:46PM +0100, Mark Broadbent wrote: > > > If what you wrote above is really correct, this means that > > Documentation/DocBook/kernel-locking.sgml contains wrong information: > > See Documentation/spin-locking.txt line 137, this states that > spin_[un]lock() should not be used in IRQ handlers. Line 137 in my spin-locking.txt is a blank line :) Please quote the exact text. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPsec performance, Miika Komu |
|---|---|
| Next by Date: | Re: [PATCH] Tulip interrupt uses non IRQ safe spinlock, Herbert Xu |
| Previous by Thread: | Re: [PATCH] Tulip interrupt uses non IRQ safe spinlock, Mark Broadbent |
| Next by Thread: | Re: [PATCH] Tulip interrupt uses non IRQ safe spinlock, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |