From: Tanya Brokhman <tlinder@codeaurora.org>
To: dedekind1@gmail.com, richard@nod.at
Cc: linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
Tanya Brokhman <tlinder@codeaurora.org>
Subject: [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling
Date: Sun, 26 Oct 2014 15:49:02 +0200 [thread overview]
Message-ID: <1414331342-27839-1-git-send-email-tlinder@codeaurora.org> (raw)
One of the limitations of the NAND devices is the method used to read
NAND flash memory may cause bit-flips on the surrounding cells and result
in uncorrectable ECC errors. This is known as the read disturb or data
retention.
Today’s Linux NAND drivers implementation doesn’t address the read disturb
and the data retention limitations of the NAND devices. To date these
issues could be overlooked since the possibility of their occurrence in
today’s NAND devices is very low.
With the evolution of NAND devices and the requirement for a “long life”
NAND flash, read disturb and data retention can no longer be ignored
otherwise there will be data loss over time.
The following patch set implements handling of Read-disturb and Data
retention by the UBI layer.
Changes from V1:
- Documentation file was added in the first patch that describes the
design in general.
All other patches were unchanged and resent just for reference. Still
working on comments from Richard on fastmap layout.
All comments that were made for V1 will be addressed in the next patch
set. This version is just for the addition of the documentation file.
Tanya Brokhman (5):
mtd: ubi: Read disturb infrastructure
mtd: ubi: Fill read disturb statistics
mtd: ubi: Make in_wl_tree function public
mtd: ubi: Read threshold verification
mtd: ubi: Add sysfs entry to force all pebs' scan
Documentation/mtd/ubi/ubi-read-disturb.txt | 145 ++++++++++++++++
drivers/mtd/ubi/attach.c | 137 +++++++++++----
drivers/mtd/ubi/build.c | 81 +++++++++
drivers/mtd/ubi/debug.c | 11 ++
drivers/mtd/ubi/eba.c | 7 +-
drivers/mtd/ubi/fastmap.c | 132 +++++++++++---
drivers/mtd/ubi/io.c | 28 +++
drivers/mtd/ubi/ubi-media.h | 32 +++-
drivers/mtd/ubi/ubi.h | 62 ++++++-
drivers/mtd/ubi/vtbl.c | 6 +-
drivers/mtd/ubi/wl.c | 270 +++++++++++++++++++++++++++--
11 files changed, 835 insertions(+), 76 deletions(-)
create mode 100644 Documentation/mtd/ubi/ubi-read-disturb.txt
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Tanya Brokhman <tlinder@codeaurora.org>
To: dedekind1@gmail.com, richard@nod.at
Cc: linux-arm-msm@vger.kernel.org, linux-mtd@lists.infradead.org,
Tanya Brokhman <tlinder@codeaurora.org>
Subject: [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling
Date: Sun, 26 Oct 2014 15:49:02 +0200 [thread overview]
Message-ID: <1414331342-27839-1-git-send-email-tlinder@codeaurora.org> (raw)
One of the limitations of the NAND devices is the method used to read
NAND flash memory may cause bit-flips on the surrounding cells and result
in uncorrectable ECC errors. This is known as the read disturb or data
retention.
Today’s Linux NAND drivers implementation doesn’t address the read disturb
and the data retention limitations of the NAND devices. To date these
issues could be overlooked since the possibility of their occurrence in
today’s NAND devices is very low.
With the evolution of NAND devices and the requirement for a “long life”
NAND flash, read disturb and data retention can no longer be ignored
otherwise there will be data loss over time.
The following patch set implements handling of Read-disturb and Data
retention by the UBI layer.
Changes from V1:
- Documentation file was added in the first patch that describes the
design in general.
All other patches were unchanged and resent just for reference. Still
working on comments from Richard on fastmap layout.
All comments that were made for V1 will be addressed in the next patch
set. This version is just for the addition of the documentation file.
Tanya Brokhman (5):
mtd: ubi: Read disturb infrastructure
mtd: ubi: Fill read disturb statistics
mtd: ubi: Make in_wl_tree function public
mtd: ubi: Read threshold verification
mtd: ubi: Add sysfs entry to force all pebs' scan
Documentation/mtd/ubi/ubi-read-disturb.txt | 145 ++++++++++++++++
drivers/mtd/ubi/attach.c | 137 +++++++++++----
drivers/mtd/ubi/build.c | 81 +++++++++
drivers/mtd/ubi/debug.c | 11 ++
drivers/mtd/ubi/eba.c | 7 +-
drivers/mtd/ubi/fastmap.c | 132 +++++++++++---
drivers/mtd/ubi/io.c | 28 +++
drivers/mtd/ubi/ubi-media.h | 32 +++-
drivers/mtd/ubi/ubi.h | 62 ++++++-
drivers/mtd/ubi/vtbl.c | 6 +-
drivers/mtd/ubi/wl.c | 270 +++++++++++++++++++++++++++--
11 files changed, 835 insertions(+), 76 deletions(-)
create mode 100644 Documentation/mtd/ubi/ubi-read-disturb.txt
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2014-10-26 13:49 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 13:49 Tanya Brokhman [this message]
2014-10-26 13:49 ` [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling Tanya Brokhman
2014-10-26 20:39 ` Richard Weinberger
2014-10-26 20:39 ` Richard Weinberger
2014-10-27 8:41 ` Tanya Brokhman
2014-10-27 8:41 ` Tanya Brokhman
2014-10-27 8:56 ` Richard Weinberger
2014-10-27 8:56 ` Richard Weinberger
2014-10-29 11:03 ` Tanya Brokhman
2014-10-29 12:00 ` Richard Weinberger
2014-10-31 13:12 ` Tanya Brokhman
2014-10-31 15:34 ` Richard Weinberger
2014-10-31 15:39 ` Richard Weinberger
2014-10-31 22:55 ` Jeff Lauruhn (jlauruhn)
2014-11-02 13:30 ` Tanya Brokhman
2014-11-07 9:21 ` Artem Bityutskiy
2014-11-07 9:21 ` Artem Bityutskiy
2014-11-02 13:25 ` Tanya Brokhman
2014-11-06 8:07 ` Artem Bityutskiy
2014-11-06 8:07 ` Artem Bityutskiy
2014-11-06 12:16 ` Tanya Brokhman
2014-11-07 8:55 ` Artem Bityutskiy
2014-11-07 8:58 ` Artem Bityutskiy
2014-11-11 20:36 ` Tanya Brokhman
2014-11-11 20:36 ` Tanya Brokhman
2014-11-11 21:39 ` Richard Weinberger
2014-11-11 21:39 ` Richard Weinberger
2014-11-12 12:07 ` Artem Bityutskiy
2014-11-12 12:07 ` Artem Bityutskiy
2014-11-12 13:01 ` Richard Weinberger
2014-11-12 13:01 ` Richard Weinberger
2014-11-12 13:32 ` Artem Bityutskiy
2014-11-12 13:32 ` Artem Bityutskiy
2014-11-12 15:37 ` Richard Weinberger
2014-11-12 15:37 ` Richard Weinberger
2014-11-12 11:55 ` Artem Bityutskiy
2014-11-12 11:55 ` Artem Bityutskiy
2014-11-13 12:13 ` Tanya Brokhman
2014-11-13 12:13 ` Tanya Brokhman
2014-11-13 13:36 ` Artem Bityutskiy
2014-11-13 13:36 ` Artem Bityutskiy
2014-11-23 8:13 ` Tanya Brokhman
2014-11-23 8:13 ` Tanya Brokhman
2014-11-02 13:23 ` Tanya Brokhman
2014-11-02 13:54 ` Richard Weinberger
2014-11-02 14:12 ` Tanya Brokhman
2014-11-02 17:02 ` Richard Weinberger
2014-11-02 17:18 ` Tanya Brokhman
[not found] <201411101307.03225.jbe@pengutronix.de>
2014-11-10 12:35 ` Richard Weinberger
2014-11-10 13:12 ` Juergen Borleis
2014-11-11 9:23 ` Richard Weinberger
2014-11-10 13:13 ` Ricard Wanderlof
2014-11-10 13:42 ` Juergen Borleis
2014-11-10 13:52 ` Ricard Wanderlof
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=1414331342-27839-1-git-send-email-tlinder@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=dedekind1@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.