| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Locking model for NAPI drivers |
| From: | Andi Kleen <ak@xxxxxx> |
| Date: | Wed, 01 Jun 2005 08:28:04 +0200 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20050531.154847.63995530.davem@xxxxxxxxxxxxx> (David S. Miller's message of "Tue, 31 May 2005 15:48:47 -0700 (PDT)") |
| References: | <20050531.154847.63995530.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) |
"David S. Miller" <davem@xxxxxxxxxxxxx> writes: Stupid question, but... > I was doing some brainstorming to try and fix a nagging problem in > the tg3 driver which suggested that doing the SMP locking differently > might be the best and cleanest solution. > > The tg3 problem is that it can do an skb_copy() in HW IRQ disabled > context which is illegal. 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. > This fixes the skb_copy() we were doing with hw > IRQs disabled (which is illegal and triggers a > BUG() with HIGHMEM enabled). Which BUG did it trigger? -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.12-rcx networking oops, Herbert Xu |
|---|---|
| Previous by Thread: | Locking model for NAPI drivers, David S. Miller |
| Next by Thread: | Driver for MCS7780 USB-IrDA bridge chip, Lukasz Stelmach |
| Indexes: | [Date] [Thread] [Top] [All Lists] |