From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Ivan Djelic <ivan.djelic@parrot.com>
Cc: Vipin Kumar <vipin.kumar@st.com>,
Viresh KUMAR <viresh.kumar@st.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"David.Woodhouse@intel.com" <David.Woodhouse@intel.com>
Subject: Re: [PATCH] Newly erased page read workaround
Date: Fri, 01 Apr 2011 16:04:41 +0300 [thread overview]
Message-ID: <1301663081.2789.65.camel@localhost> (raw)
In-Reply-To: <20110401121447.GA19151@parrot.com>
On Fri, 2011-04-01 at 14:14 +0200, Ivan Djelic wrote:
> Did you consider this idea: if you have an unused byte available in oob,
> program it to 0x00 when a page is programmed.
I guess this depends on the the controller, but probably this could mean
a substantial write overhead, not?
> That way, you just need to check a single byte when you read a page in order
> to distinguish erased pages from programmed pages. And by counting the number
> of 1s in the byte, you can be robust to bitflips.
Could you please explain some more what do you mean? So you write the
0x00 byte. Then when you read, you count the number of "1" bits in the
byte. And what exactly this count gives you and to which bitflips you
become robust?
> As a special refinement, you could also "cleanup" pages detected as erased, in
> order to iron out possible bitflips.
What do you mean by "cleanup" a page?
Thanks!
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-01 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 6:10 [PATCH] Newly erased page read workaround Viresh Kumar
2011-02-24 9:38 ` Ivan Djelic
2011-02-24 10:20 ` Vipin Kumar
2011-02-24 11:10 ` Ivan Djelic
2011-02-24 11:36 ` Vipin Kumar
2011-03-22 4:36 ` viresh kumar
2011-03-31 13:51 ` Artem Bityutskiy
2011-04-01 6:28 ` Vipin Kumar
2011-04-01 6:51 ` Artem Bityutskiy
2011-04-01 8:33 ` Vipin Kumar
2011-04-01 8:39 ` Artem Bityutskiy
2011-04-01 9:06 ` Vipin Kumar
2011-04-01 9:42 ` Artem Bityutskiy
2011-04-01 12:14 ` Ivan Djelic
2011-04-01 13:04 ` Artem Bityutskiy [this message]
2011-04-01 14:04 ` Ivan Djelic
2011-04-01 14:16 ` Artem Bityutskiy
2011-04-01 14:49 ` Ivan Djelic
2011-04-01 14:58 ` Ricard Wanderlof
2011-04-01 15:46 ` Ivan Djelic
2011-04-01 16:09 ` Ivan Djelic
2011-04-01 16:16 ` Artem Bityutskiy
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=1301663081.2789.65.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=David.Woodhouse@intel.com \
--cc=ivan.djelic@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vipin.kumar@st.com \
--cc=viresh.kumar@st.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