From: broonie@debian.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: I/O issues with writing to mtdblock devices on kirkwood
Date: Wed, 13 Jan 2016 11:42:27 +0000 [thread overview]
Message-ID: <20160113114227.GI6588@sirena.org.uk> (raw)
In-Reply-To: <6044522.tqmlJ5a48h@wuerfel>
On Tue, Jan 12, 2016 at 11:41:45PM +0100, Arnd Bergmann wrote:
> On Tuesday 12 January 2016 22:00:58 Mark Brown wrote:
> > There's also the potential for the overhead from interrupts to be worse
> > than the overhead for busy waiting, but given how badly we're coping now
> > it's worth another look.
> Possible, yes. Right now, we do a udelay(1), which I think waits between one and
> two microseconds normally, so we are probably adding extra latency of under
> one microsecond per byte by not polling constantly. If the interrupt latency
> from device-ready to entering the code is more than that, we can assume that
> the transfer ends up being slower. There is also some time spent for getting
> back out of the interrupt handler, but that's no worse than doing nothing
> in udelay().
Indeed. It may also make the cache performance worse as a result of
frequently switching to the interrupt handler but if nothing else it
should make it easier for something else to get access to the CPU which
seems to be the issue here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160113/1928c3a6/attachment.sig>
prev parent reply other threads:[~2016-01-13 11:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 12:24 I/O issues with writing to mtdblock devices on kirkwood Ian Campbell
2015-08-21 13:07 ` Andrew Lunn
2015-08-21 20:23 ` Ian Campbell
2015-09-05 21:08 ` Andrew Lunn
2015-09-06 12:11 ` Ian Campbell
2015-10-11 14:37 ` JM
2015-10-11 15:35 ` Andrew Lunn
2015-10-12 14:29 ` JM
2015-10-12 16:05 ` Rob J. Epping
2015-10-12 16:21 ` Andrew Lunn
2015-10-13 7:51 ` Ian Campbell
[not found] ` <5626B4DC.8000407@mcfarlanes.me>
[not found] ` <5627F4E8.3030907@mcfarlanes.me>
2015-10-21 21:11 ` Ian Campbell
2015-10-21 21:22 ` Iain McFarlane
2015-10-21 21:28 ` JM
2015-10-21 21:31 ` Iain McFarlane
2015-10-22 0:38 ` Andrew Lunn
2015-10-22 6:40 ` Ian Campbell
2015-10-22 6:40 ` Ian Campbell
2016-01-11 23:00 ` Martin Michlmayr
2016-01-11 23:22 ` Mark Brown
2016-01-11 23:43 ` Andrew Lunn
2016-01-12 1:21 ` Mark Brown
2016-01-12 0:07 ` Martin Michlmayr
2016-01-12 0:47 ` Mark Brown
2016-01-12 1:19 ` Andrew Lunn
2016-01-12 1:31 ` Mark Brown
2016-01-12 16:29 ` Arnd Bergmann
2016-01-12 18:02 ` Mark Brown
2016-01-12 21:49 ` Arnd Bergmann
2016-01-12 22:00 ` Mark Brown
2016-01-12 22:41 ` Arnd Bergmann
2016-01-13 11:42 ` Mark Brown [this message]
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=20160113114227.GI6588@sirena.org.uk \
--to=broonie@debian.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.