From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Alan Stern <stern@rowland.harvard.edu>, Ben Dooks <ben-linux@fluff.org>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@lists.codethink.co.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: host: ehci: allow tine of highspeed nak-count
Date: Fri, 16 Nov 2018 12:53:57 +0000 [thread overview]
Message-ID: <39eb9e8b-2b5d-ea75-3232-be77c3743dbc@codethink.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1811141338100.1637-100000@iolanthe.rowland.org>
On 14/11/18 18:47, Alan Stern wrote:
> On Wed, 14 Nov 2018, Ben Dooks wrote:
>
>> From: Ben Dooks <ben.dooks@codethink.co.uk>
>>
>> At least some systems benefit with less scheduling if the NAK count
>> value is set higher than the default 4. For instance a Tegra3 with
>> an SMSC9512 showed less interrupt load when this was changed to 14.
>
> Interesting. Why do you think this is? In theory, increasing the NAK
> count RL value should cause a higher memory bus load and perhaps a
> slight rise in the interrupt load (transfers will complete a little
> more quickly because the controller tries harder to poll the endpoints
> and see if they are ready).
I thought the NAK counter was decremented until the transfer is given
up on. I'm going to have to go back and get some actual figures from
a running system as this was originally done over a year ago with the
SMSC9512 (IIRC) network driver.
>> To allow the changing of this value, add a sysfs node to each of
>> the controllers to allow run-time changing.
>>
>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
>
> The patch looks okay to me.
I'll look at getting some tracing from the SMSC driver to see what
is going on.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2018-11-16 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 17:13 Ben Dooks
2018-11-14 18:47 ` Alan Stern
2018-11-16 12:53 ` Ben Dooks [this message]
2018-11-16 15:38 ` Alan Stern
2018-11-19 10:06 ` Ben Dooks
2019-01-07 16:19 ` Greg KH
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=39eb9e8b-2b5d-ea75-3232-be77c3743dbc@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=ben-linux@fluff.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®