From: Adrian Hunter <adrian.hunter@nokia.com>
To: Madhusudhan <madhu.cr@ti.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: MMC retry mechanism
Date: Mon, 07 Sep 2009 10:17:32 +0300 [thread overview]
Message-ID: <4AA4B38C.6060202@nokia.com> (raw)
In-Reply-To: <011c01ca2dac$2de779d0$544ff780@am.dhcp.ti.com>
Madhusudhan wrote:
> Hi Adrian,
>
> With respect to the below commit, It looks like currently the retry
> mechanism only handles the READ path.
>
> I wonder could a similar retry logic feasible for the WRITE path?
>
> Regards,
> Madhu
>From my point of view, writes should never fail. In theory, the MMC
should have enough reserved blocks to cover bad blocks for the
expected lifetime of the device. It should then be just copying
and remapping to avoid having to return write errors.
Of course, a lot of cards probably don't do that right. However,
I think maybe the block layer already retries failed writes.
>
>
>
> commit 6a79e391df295bd7c2aa1309ea5031f361c197fd
> Author: Adrian Hunter <ext-adrian.hunter@nokia.com>
> Date: Wed Dec 31 18:21:17 2008 +0100
>
>
>
> mmc_block: ensure all sectors that do not have errors are read
>
> If a card encounters an ECC error while reading a sector it will
>
> timeout. Instead of reporting the entire I/O request as having
>
> an error, redo the I/O one sector at a time so that all readable
>
> sectors are provided to the upper layers.
>
>
>
> Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
>
> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
>
>
next prev parent reply other threads:[~2009-09-07 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 22:08 MMC retry mechanism Madhusudhan
2009-09-06 14:20 ` Pierre Ossman
2009-09-06 17:58 ` Madhusudhan
2009-09-14 19:37 ` Pierre Ossman
2009-09-07 7:17 ` Adrian Hunter [this message]
2009-09-10 21:20 ` Madhusudhan
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=4AA4B38C.6060202@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=madhu.cr@ti.com \
/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