On Wednesday 30 March 2011, Andrei Warkentin wrote: > On Tue, Mar 29, 2011 at 2:01 AM, Arnd Bergmann <[email protected]> wrote: > > On Tuesday 29 March 2011, Andrei Warkentin wrote: > >> On Fri, Mar 25, 2011 at 10:14 AM, Arnd Bergmann <[email protected]> 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 <[email protected]> Chris, what is your opinion on the patch? Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
