From: David Brown <davidb@davidb.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
Alexey Korolev <akorolev@infradead.org>
Subject: Re: Limited support of NAND features in MTD.
Date: Tue, 18 Dec 2007 08:57:58 -0800 [thread overview]
Message-ID: <20071218165758.GA11634@old.davidb.org> (raw)
In-Reply-To: <20071218151800.GG1741@lazybastard.org>
On Tue, Dec 18, 2007 at 04:18:01PM +0100, Jörn Engel wrote:
>> Yeah. I know this feature. If I properly understand the real purpose of
>> it is mostly related for FTL but could be used for FS as well.
>> You are right it make sense to try it. But I do not know when it will be possible to do
>> this. Usually this feature is called as Internal data move in NAND specs.
>
>At least I would like to know what the conditions are. Can the command
>copy whole blocks only? If it can copy single pages, can it copy any
>pages or just the Nth page of one block to the Nth page of another?
One problem with the on-chip copy is that ECC doesn't get corrected. If
there are errors on readback, it will get written that way, and errors
would accumulate.
It is conceivable that the controller could do something intermediary, such
as read the data, and if the ECC needs no correction, write from the
on-chip cache, otherwise write the corrected data.
Dave
next prev parent reply other threads:[~2007-12-18 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 11:51 Limited support of NAND features in MTD Alexey Korolev
2007-12-12 13:54 ` Artem Bityutskiy
2007-12-12 14:36 ` Josh Boyer
2007-12-13 17:47 ` Alexey Korolev
2007-12-18 14:23 ` Jörn Engel
2007-12-18 15:06 ` Alexey Korolev
2007-12-18 15:18 ` Jörn Engel
2007-12-18 15:46 ` Alexey Korolev
2007-12-18 16:07 ` Alexey Korolev
2007-12-18 16:57 ` David Brown [this message]
2007-12-18 16:56 ` Jörn Engel
2007-12-18 18:14 ` David Woodhouse
2007-12-19 10:49 ` Alexey Korolev
2007-12-19 10:52 ` David Woodhouse
2007-12-19 11:55 ` Alexey Korolev
2007-12-19 11:57 ` Artem Bityutskiy
2007-12-19 12:47 ` David Woodhouse
2007-12-18 15:48 ` Alexander Belyakov
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=20071218165758.GA11634@old.davidb.org \
--to=davidb@davidb.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.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