From: Artem Bityutskiy <dedekind1@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Iwo Mergler <Iwo.Mergler@netcommwireless.com>,
"Jeff Lauruhn \(jlauruhn\)" <jlauruhn@micron.com>,
Richard Weinberger <richard@nod.at>,
Andrea Scian <rnd4@dave-tech.it>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Andrea Marson <andrea.marson@dave.eu>
Subject: Re: RFC: detect and manage power cut on MLC NAND
Date: Tue, 24 Mar 2015 09:05:16 +0200 [thread overview]
Message-ID: <1427180716.8234.136.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20150323200511.545210ad@bbrezillon>
On Mon, 2015-03-23 at 20:05 +0100, Boris Brezillon wrote:
> > If we sacrifice another page, we could store a copy of the VID header
> > there, in case the first copy gets corrupted. IOW, we'd have:
> >
> > ECH, VIDH#1, VIDH#2, User Data.
>
> What do you mean by 'sacrificing another page', are you talking about
> the one paired with the VID header page ?
> If that's the case, then we cannot write anything on it (even a VID
> header backup), because if the PROGRAM operation is interrupted both
> pages (VIDH#1 and #2) could be corrupted.
Just this:
Page 0: ECH
Page 1: VIDH#1 (+all the ECH data)
Page 2: VIDH#2 (same as VIDH#1)
VIDH#1 and #2 are not in paired pages, so I expect one of them to always
be good.
If pages 0,1;2,3;4,5;etc are paired, we may lose ECH sometimes, should
not be catastrophic. I wonder though, if this pairing scheme is
realistic?
In case of a larger pairing step we seem to be always OK and will always
have a valid ECH and VIDH.
Do I miss something?
next prev parent reply other threads:[~2015-03-24 7:05 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 11:57 RFC: detect and manage power cut on MLC NAND Andrea Scian
2015-03-10 12:51 ` Richard Weinberger
2015-03-11 7:20 ` Artem Bityutskiy
2015-03-11 8:57 ` Richard Weinberger
2015-03-11 9:05 ` Artem Bityutskiy
2015-03-11 9:09 ` Richard Weinberger
2015-03-11 17:01 ` Andrea Scian
2015-03-11 17:23 ` Jeff Lauruhn (jlauruhn)
2015-03-11 17:29 ` Richard Weinberger
2015-03-11 21:16 ` Jeff Lauruhn (jlauruhn)
2015-03-12 10:28 ` Richard Weinberger
2015-03-12 22:57 ` Jeff Lauruhn (jlauruhn)
2015-03-13 20:31 ` Boris Brezillon
2015-03-13 23:51 ` Jeff Lauruhn (jlauruhn)
2015-03-14 9:46 ` Andrea Marson - DAVE Embedded Systems
2015-03-16 16:02 ` Jeff Lauruhn (jlauruhn)
2015-03-17 8:00 ` Andrea Scian
2015-03-14 10:32 ` Boris Brezillon
2015-03-16 21:11 ` Jeff Lauruhn (jlauruhn)
2015-03-17 9:30 ` Andrea Scian
2015-03-17 10:02 ` Boris Brezillon
2015-03-17 16:42 ` Jeff Lauruhn (jlauruhn)
2015-03-18 8:45 ` RFC: detect and manage power cut on MLC NAND (linux-mtd Digest, Vol 144, Issue 70) Andrea Marson
2015-03-18 9:07 ` Boris Brezillon
2015-03-18 9:56 ` Andrea Marson
2015-03-18 10:03 ` Boris Brezillon
2015-03-18 12:07 ` Richard Weinberger
2015-03-18 17:11 ` Jeff Lauruhn (jlauruhn)
2015-03-18 16:12 ` Jeff Lauruhn (jlauruhn)
2015-03-19 8:47 ` RFC: detect and manage power cut on MLC NAND Andrea Marson
2015-03-19 9:12 ` Boris Brezillon
2015-03-19 17:45 ` Jeff Lauruhn (jlauruhn)
2015-03-20 0:25 ` Iwo Mergler
2015-03-20 3:38 ` nick
2015-03-20 5:40 ` Iwo Mergler
2015-03-20 8:26 ` Boris Brezillon
2015-03-20 17:15 ` Nick Krause
2015-03-22 23:45 ` Iwo Mergler
2015-03-23 2:18 ` Iwo Mergler
2015-03-23 7:06 ` Artem Bityutskiy
2015-03-23 19:05 ` Boris Brezillon
2015-03-24 7:05 ` Artem Bityutskiy [this message]
2015-03-19 18:00 ` Jeff Lauruhn (jlauruhn)
2015-03-20 8:07 ` Andrea Marson
2015-03-17 17:04 ` Jeff Lauruhn (jlauruhn)
2015-03-16 9:01 ` Ricard Wanderlof
2015-03-16 17:27 ` Jeff Lauruhn (jlauruhn)
2015-03-14 10:03 ` Richard Weinberger
2015-03-12 9:32 ` Ricard Wanderlof
2015-03-23 4:08 ` Iwo Mergler
2015-03-23 21:15 ` Jeff Lauruhn (jlauruhn)
2015-03-24 1:17 ` Iwo Mergler
2015-03-24 16:50 ` Jeff Lauruhn (jlauruhn)
2015-03-25 3:38 ` Iwo Mergler
2015-03-25 8:33 ` Ricard Wanderlof
2015-03-26 1:57 ` Jeff Lauruhn (jlauruhn)
2015-03-26 8:55 ` Ricard Wanderlof
2015-03-11 7:21 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2015-03-12 10:31 Andrea Marson - DAVE Embedded Systems
[not found] <mailman.37176.1426610573.22890.linux-mtd@lists.infradead.org>
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=1427180716.8234.136.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Iwo.Mergler@netcommwireless.com \
--cc=andrea.marson@dave.eu \
--cc=boris.brezillon@free-electrons.com \
--cc=jlauruhn@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=rnd4@dave-tech.it \
/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).