Re: [PATCH net-next] usbnet: use netif_tx_wake_queue instead of netif_start_queue

Am Mittwoch, 14. März 2012, 15:00:24 schrieb Alexey Orishko:

If host is going to autosuspend function with two interfaces and
if IP packet has arrived in-between of two usbnet_suspend() callbacks,
i.e usbnet_resume() is called in-between, tx data flow is stopped.
When autosuspend timer expires and device is put to autosuspend
again, tx queue is waked up and data can be sent again.
This behavior might be repeated several times in a row.

Tested on Intel/ARM.

Reviewed-by: Sjur Brændeland <sjur.brandeland-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Tested-by: Dmitry Tarnyagin <dmitry.tarnyagin-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
Signed-off-by: Alexey Orishko <alexey.orishko-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>

Acked-by: Oliver Neukum <redacted>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

From: Oliver Neukum <redacted>
Date: Thu, 15 Mar 2012 18:05:09 +0100

Am Mittwoch, 14. März 2012, 15:00:24 schrieb Alexey Orishko:

quoted

If host is going to autosuspend function with two interfaces and
if IP packet has arrived in-between of two usbnet_suspend() callbacks,
i.e usbnet_resume() is called in-between, tx data flow is stopped.
When autosuspend timer expires and device is put to autosuspend
again, tx queue is waked up and data can be sent again.
This behavior might be repeated several times in a row.

Tested on Intel/ARM.

Reviewed-by: Sjur Brændeland <redacted>
Tested-by: Dmitry Tarnyagin <redacted>
Signed-off-by: Alexey Orishko <redacted>

Acked-by: Oliver Neukum <redacted>

Applied, thanks.