On Tue, 08 Sep 2009 12:40:23 -0400 Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > On Tue, 2009-09-08 at 09:11 -0700, Stephen Hemminger wrote: > > > > > Process context is too slow. > > > > > > Well, I'm hoping to prove the opposite. I'm working on some stuff that I > > > plan to present at Linux Plumbers. I've been too distracted by other > > > things, but hopefully I'll have some good numbers to present by then. > > > > > > > > > That's great, does it keep the good properties of NAPI (irq disabling > > and throttling?) > > Not exactly sure what you mean by throttling, but I'm assuming it will. > > As for irqs disabling, I'm trying to avoid doing that. Note, the device > will have its interrupts disabled, but not all other devices will. > > -- Steve > > The way NAPI works is that in irq routine, the device disables interrupts then schedules processing packets, when processing is done irq's are re-enabled. This means that if machine is being flooded, irq's stay off, and the packets get discarded (because device hardware ring is full), rather than in software (because software receive queue is full). -- -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
