| To: | akpm@xxxxxxxxx |
|---|---|
| Subject: | Re: Info: NAPI performance at "low" loads |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Tue, 17 Sep 2002 14:39:47 -0700 (PDT) |
| Cc: | manfred@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <3D87A264.8D5F3AD2@xxxxxxxxx> |
| References: | <3D879F59.6BDF9443@xxxxxxxxx> <20020917.142635.114214508.davem@xxxxxxxxxx> <3D87A264.8D5F3AD2@xxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Andrew Morton <akpm@xxxxxxxxx> Date: Tue, 17 Sep 2002 14:45:08 -0700 "David S. Miller" wrote: > Well, it is due to the same problems manfred saw initially, > namely just a crappy or buggy NAPI driver implementation. :-) It was due to additional inl()'s and outl()'s in the driver fastpath. How many? Did the implementation cache the register value in a software state word or did it read the register each time to write the IRQ masking bits back? It is issues like this that make me say "crappy or buggy NAPI implementation" Any driver should be able to get the NAPI overhead to max out at 2 PIOs per packet. And if the performance is really concerning, perhaps add an option to use MEM space in the 3c59x driver too, IO instructions are constant cost regardless of how fast the PCI bus being used is :-) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Info: NAPI performance at "low" loads, Andrew Morton |
|---|---|
| Next by Date: | Re: Info: NAPI performance at "low" loads, Jeff Garzik |
| Previous by Thread: | Re: Info: NAPI performance at "low" loads, Andrew Morton |
| Next by Thread: | Re: Info: NAPI performance at "low" loads, Jeff Garzik |
| Indexes: | [Date] [Thread] [Top] [All Lists] |