From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>
Cc: Linux USB <linux-usb@vger.kernel.org>,
David Miller <davem@davemloft.net>,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: u_ether: remove interrupt throttling
Date: Tue, 1 Nov 2016 14:21:14 +0200 [thread overview]
Message-ID: <20161101122114.GR4617@intel.com> (raw)
In-Reply-To: <20161101112959.19640-1-felipe.balbi@linux.intel.com>
On Tue, Nov 01, 2016 at 01:29:59PM +0200, Felipe Balbi wrote:
> According to Dave Miller "the networking stack has a
> hard requirement that all SKBs which are transmitted
> must have their completion signalled in a fininte
> amount of time. This is because, until the SKB is
> freed by the driver, it holds onto socket,
> netfilter, and other subsystem resources."
>
> In summary, this means that using TX IRQ throttling
> for the networking gadgets is, at least, complex and
> we should avoid it for the time being.
>
> Cc: <stable@vger.kernel.org>
> Reported-by: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> Suggested-by: David Miller <davem@davemloft.net>
> Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Fixes laggy/hangy g_ether on my BYT FFRD8 tablet, caused by
commit 55a0237f8f47 ("usb: dwc3: gadget: use allocated/queued reqs for LST bit")
Tested-by: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> ---
> drivers/usb/gadget/function/u_ether.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/usb/gadget/function/u_ether.c b/drivers/usb/gadget/function/u_ether.c
> index f4a640216913..119a2e5848e8 100644
> --- a/drivers/usb/gadget/function/u_ether.c
> +++ b/drivers/usb/gadget/function/u_ether.c
> @@ -589,14 +589,6 @@ static netdev_tx_t eth_start_xmit(struct sk_buff *skb,
>
> req->length = length;
>
> - /* throttle high/super speed IRQ rate back slightly */
> - if (gadget_is_dualspeed(dev->gadget))
> - req->no_interrupt = (((dev->gadget->speed == USB_SPEED_HIGH ||
> - dev->gadget->speed == USB_SPEED_SUPER)) &&
> - !list_empty(&dev->tx_reqs))
> - ? ((atomic_read(&dev->tx_qlen) % dev->qmult) != 0)
> - : 0;
> -
> retval = usb_ep_queue(in, req, GFP_ATOMIC);
> switch (retval) {
> default:
> --
> 2.10.1
--
Ville Syrj�l�
Intel OTC
next prev parent reply other threads:[~2016-11-01 12:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 11:29 [PATCH] usb: gadget: u_ether: remove interrupt throttling Felipe Balbi
2016-11-01 12:21 ` Ville Syrjälä [this message]
2016-11-02 6:02 ` Peter Chen
2016-11-02 7:55 ` Felipe Balbi
2016-11-02 8:36 ` Peter Chen
2016-11-02 11:02 ` Felipe Balbi
2016-11-03 0:32 ` Peter Chen
2016-11-03 8:36 ` Felipe Balbi
2016-11-02 15:22 ` David Miller
2016-11-03 0:23 ` Peter Chen
2016-11-03 7:04 ` Felipe Balbi
2016-11-03 9:03 ` Peter Chen
2016-11-03 9:53 ` Peter Chen
2016-11-03 10:48 ` Felipe Balbi
2016-11-04 2:11 ` Peter Chen
2016-11-07 12:36 ` Felipe Balbi
2016-11-08 1:42 ` Peter Chen
2016-11-03 10:42 ` Felipe Balbi
2016-11-04 1:12 ` Peter Chen
2016-11-04 1:14 ` Peter Chen
2016-11-03 17:04 ` David Miller
2016-11-07 12:39 ` Felipe Balbi
2016-11-07 15:50 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161101122114.GR4617@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=davem@davemloft.net \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).