In this case, the system can potentially be interrupted too
often(assuming an interrupt per frame received and transmitted,
it comes to nearly interrupt every few 10s of uSecs). So, though the
packet processing doesnt take much time(involving movement of skbs
and modifying few fields), there is a hidden cost of context
swaps(kernel isr, bh, user space)
I am not sure of the effect of this on performance..
Sounds like a HW design issue you need to address. Perhaps it would be
better to interrupt on buffer full or some sort of data ready but timeout
condition. It is good to be concerned about IRQ but this does not affect CPM
performance...
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/