From: Artem Bityutskiy <dedekind@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "David Brown" <davidb@davidb.org>, "Jörn Engel" <joern@logfs.org>,
linux-mtd@lists.infradead.org,
"Alexey Korolev" <akorolev@infradead.org>
Subject: Re: Limited support of NAND features in MTD.
Date: Wed, 19 Dec 2007 13:57:23 +0200 [thread overview]
Message-ID: <1198065443.18962.40.camel@sauron> (raw)
In-Reply-To: <1198061571.13978.733.camel@pmac.infradead.org>
On Wed, 2007-12-19 at 10:52 +0000, David Woodhouse wrote:
> On Wed, 2007-12-19 at 10:49 +0000, Alexey Korolev wrote:
> > Hmm I did not heard about this. Could you please give more details on
> > how partial page read can suffer from lack of ECC?
>
> If your ECC covers the whole page, you have to read the whole page in
> order to check ECC.
>
> Of course, if you do ECC in sub-pages in the first place, you can read
> only a single ECC block. But you still can't just read arbitrary byte
> ranges.
Sure, but as the guys showed, even this gives substantial JFFS2
performance growth. Providing their figures are correct, subpage reads
are more then worth using.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2007-12-19 12:40 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
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 [this message]
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=1198065443.18962.40.camel@sauron \
--to=dedekind@infradead.org \
--cc=akorolev@infradead.org \
--cc=davidb@davidb.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