From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] MMC: error handling improvements
Date: Thu, 17 Feb 2011 10:40:48 +0000 [thread overview]
Message-ID: <20110217104048.GD24627@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1297882866.20252.20.camel@hornet.cambridge.arm.com>
On Wed, Feb 16, 2011 at 07:01:06PM +0000, Pawel Moll wrote:
> / # dd if=/dev/mmcblk0 of=/dev/null bs=128k count=10
> 10+0 records in
> 10+0 records out
> 1310720 bytes (1.3MB) copied, 46.539866 seconds, 27.5KB/s
> / # sleep 30
> / # dd if=/dev/mmcblk0 of=/dev/null bs=128k count=10
> 10+0 records in
> 10+0 records out
> 1310720 bytes (1.3MB) copied, 46.540215 seconds, 27.5KB/s
>
>
> So it does the right thing with decreasing the clock rate in face of
> problems, I just can't see it clocking it back up...
You need at least 100 requests before it'll consider clocking back up.
Once it has 100 requests, no more than 5% of them at the current clock
rate must have failed for it to consider clocking up. I found with
fewer requests, it was forever clocking down, up, down very frequently.
prev parent reply other threads:[~2011-02-17 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 23:03 [RFC] MMC: error handling improvements Russell King - ARM Linux
2011-02-15 23:49 ` David Brown
2011-02-16 18:41 ` Linus Walleij
2011-02-16 19:28 ` David Brown
2011-02-16 21:01 ` Linus Walleij
2011-02-16 23:06 ` Brian Swetland
2011-02-18 13:03 ` Linus Walleij
2011-02-18 16:04 ` Brian Swetland
2011-02-21 20:49 ` Linus Walleij
[not found] ` <AANLkTimpJUoc64py_jCrvsrXscawsR2c7JBtr1e0U+e8@mail.gmail.com>
2011-03-01 18:39 ` Fwd: " Murali Krishna Palnati
2011-03-01 20:22 ` Russell King - ARM Linux
2011-03-02 10:12 ` Linus Walleij
2011-02-19 15:00 ` Russell King - ARM Linux
2011-03-01 13:28 ` Sahitya Tummala
2011-02-16 19:01 ` Pawel Moll
2011-02-17 10:40 ` Russell King - ARM Linux [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=20110217104048.GD24627@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 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).