From: Ben Dooks <ben@fluff.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
Ben Dooks <ben-linux@fluff.org>,
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: Mon, 19 Nov 2018 10:06:28 +0000 [thread overview]
Message-ID: <20181119100628.iukzaouikfsbrywq@hetzy.fluff.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1811161034500.1487-100000@iolanthe.rowland.org>
On Fri, Nov 16, 2018 at 10:38:18AM -0500, Alan Stern wrote:
> On Fri, 16 Nov 2018, Ben Dooks wrote:
>
> > 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.
>
> That's right. So if the RL value is higher, there will be more polling
> attempts in quick succession before the NAK counter drops to 0 and the
> controller gives up. More polling attempts in quick succession means
> heavier memory bus usage.
>
> > 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.
>
> Okay. Should we consider the patch to be held in suspense until then?
Yes, I'm not going to have access to any of the test hardware until the
end of the week, and will re-verify my initial notes from last year.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
next prev parent reply other threads:[~2018-11-19 10:35 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
2018-11-16 15:38 ` Alan Stern
2018-11-19 10:06 ` Ben Dooks [this message]
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=20181119100628.iukzaouikfsbrywq@hetzy.fluff.org \
--to=ben@fluff.org \
--cc=ben-linux@fluff.org \
--cc=ben.dooks@codethink.co.uk \
--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®