From: Arnd Bergmann <arnd@arndb.de>
To: Andrei Warkentin <andreiw@motorola.com>
Cc: linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>
Subject: Re: [comments] MMC: Reliable write support.
Date: Wed, 30 Mar 2011 14:05:20 +0200 [thread overview]
Message-ID: <201103301405.21047.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTinDdEJ0bwH3Kj_QmhD=Z=07eaRvpA=sASn+DmkJ@mail.gmail.com>
On Wednesday 30 March 2011, Andrei Warkentin wrote:
> On Tue, Mar 29, 2011 at 2:01 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 29 March 2011, Andrei Warkentin wrote:
> >> On Fri, Mar 25, 2011 at 10:14 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> >>
> >> I confirmed with two MMC vendors that there is no "flush". Once the
> >> DAT transfer completes, the data is stored on non-volatile storage as
> >> soon as the busy status is cleared.
> >>
> >> Reliable writes are still "more reliable" because if the DAT transfer
> >> is interrupted (power or reset through CMD0/CMD15 or hw pin for eMMC),
> >> you have predictable flash contents. So it makes sense to map REQ_FUA
> >> to it (and REQ_META, I would guess).
> >
> > Yes, sounds good.
> >
> > So I guess on MLC flash, a reliable write will go to a flash page
> > that does not have data in any of its paired pages.
>
> Should I resubmit the patch?
I think the patch was ok, you can add my
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Chris, what is your opinion on the patch?
Arnd
next prev parent reply other threads:[~2011-03-30 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 21:22 Reliable write support Andrei Warkentin
2011-03-24 21:22 ` [comments] MMC: " Andrei Warkentin
2011-03-25 15:14 ` Arnd Bergmann
2011-03-26 7:17 ` Andrei Warkentin
2011-03-26 7:22 ` Andrei Warkentin
2011-03-29 0:50 ` Andrei Warkentin
2011-03-29 7:01 ` Arnd Bergmann
2011-03-29 22:44 ` Andrei Warkentin
2011-03-30 12:05 ` Arnd Bergmann [this message]
2011-03-30 22:38 ` Chris Ball
2011-03-31 20:39 ` Andrei Warkentin
2011-03-31 20:58 ` Chris Ball
2011-03-31 23:40 ` [PATCH] " Andrei Warkentin
2011-04-01 0:47 ` Chris Ball
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=201103301405.21047.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=andreiw@motorola.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.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