Matthew Wilcox wrote:
> > 1. Interrupt comes in
> > 2. Kernel disables interrupt
> > 3. Driver fetches/sends data.
> > 4. Driver loops back to 3 if there's more data
> > (many drivers do this already).
> > 5. Driver returns.
> >
> > ... timer driven delay ...
> >
> > 6. Kernel reenables interrupt.
> > 7. If interrupt pending, go to 2.
>
> You could only do this if the interrupt is not shared. But if your
> network is normally being hammered then you probably didn't configure
> your network card to be on the same interrupt as your hard disc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/