From: "Jörn Engel" <joern@logfs.org>
To: Alexey Korolev <akorolev@infradead.org>
Cc: dwmw2@infradead.org, joern@logfs.org, linux-mtd@lists.infradead.org
Subject: Re: Limited support of NAND features in MTD.
Date: Tue, 18 Dec 2007 15:23:35 +0100 [thread overview]
Message-ID: <20071218142335.GD1741@lazybastard.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0712121107010.19025@pentafluge.infradead.org>
On Wed, 12 December 2007 11:51:40 +0000, Alexey Korolev wrote:
>
> It is not a secret that current MTD supports very limited set of NAND
> features. Some of missed features like partial page read or cached read
> are able to improve file system performance and its implementation do
> not require s/w redesign.
What does cached read do?
Another feature that could become useful would be the on-chip copying.
With JFFS2 this is rare, but when doing GC or wear leveling in a fashion
that keeps certain alignments intact, it could improve performance.
Jörn
--
The cost of changing business rules is much more expensive for software
than for a secretaty.
-- unknown
next prev parent reply other threads:[~2007-12-18 14:29 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 [this message]
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
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=20071218142335.GD1741@lazybastard.org \
--to=joern@logfs.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.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 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.