| To: | ak@xxxxxx (Andi Kleen) |
|---|---|
| Subject: | Re: Locking model for NAPI drivers |
| From: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 01 Jun 2005 18:42:43 +1000 |
| Cc: | davem@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <m1fyw2wpzf.fsf@xxxxxx> |
| Organization: | Core |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | tin/1.7.4-20040225 ("Benbecula") (UNIX) (Linux/2.4.27-hx-1-686-smp (i686)) |
Andi Kleen <ak@xxxxxx> wrote: > > That is because of the kmap_atomic it does right? At least in the i386 > highmem implementation I don't see any code that would be less safe in > hard interrupt context compared to BHs. And FRV and mips look like they > allow it too. To make it safe we'll have to allocate another precious km_type entry. -- 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: Locking model for NAPI drivers, Greg Banks |
|---|---|
| Next by Date: | Unable to handle kernel paging request at virtual address 04000460, raghunathan.venkatesan |
| Previous by Thread: | Re: Locking model for NAPI drivers, Greg Banks |
| Next by Thread: | Re: Locking model for NAPI drivers, Michael Chan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |