search for: eip_interrupt

...ct net_device *dev); > > struct net_device_stats *ei_get_stats(struct net_device *dev); > > @@ -50,7 +50,7 @@ void NS8390p_init(struct net_device *dev, int startp); > > int eip_open(struct net_device *dev); > > int eip_close(struct net_device *dev); > > irqreturn_t eip_interrupt(int irq, void *dev_id); > > -void eip_tx_timeout(struct net_device *dev); > > +void eip_tx_timeout(struct net_device *dev, unsigned int txqueue); > > netdev_tx_t eip_start_xmit(struct sk_buff *skb, struct net_device *dev); > > void eip_set_multicast_list(struct net_device...

This series add two important features. One of them changes the .ndo_tx_timeout to include an extra parameter to identify the stuck queue. Many drivers are using a nester loop to identify which queue is stooped/stucked. This is a redundant work since dev_watchdog is doing exactly the same thing. This is so interesting for other drivers to in terms of code optimization. The second part (second

This series add two important features. One of them changes the .ndo_tx_timeout to include an extra parameter to identify the stuck queue. Many drivers are using a nester loop to identify which queue is stooped/stucked. This is a redundant work since dev_watchdog is doing exactly the same thing. This is so interesting for other drivers to in terms of code optimization. The second part (second

Yet another forward declaration I missed. Hopfully the last one ... A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.