From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
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: Wed, 12 Dec 2007 08:36:39 -0600 [thread overview]
Message-ID: <20071212083639.337f3049@weaponx> (raw)
In-Reply-To: <Pine.LNX.4.64.0712121107010.19025@pentafluge.infradead.org>
On Wed, 12 Dec 2007 11:51:40 +0000 (GMT)
Alexey Korolev <akorolev@infradead.org> wrote:
> Hi,
>
> 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.
>
> I have a question is there any limitations/restrictions to support extended features?
> Does it make sense to implement these features and manage them
> through nand_chip->options flag, letting people to choose whether to use
> features or not? If it is not a good idea what is the best way to manage
> it?
>
> Currently my clooeague and I did prototypes of partial page read and cached read
> functionalities showing performance increase. For example partial page read showed about 20%
> of file open/stat time performance increase in JFFS2 on LP NAND. Cached
> read increases overall read performance but value strongly depends on
> platform IO latencies. Now we are thinking to create and sent patches.
>
> So your suggestions/recomendations are welcome!
Here is my suggestion. Create the patches and send them :).
More seriously, it is often better to send out patches to show more
concretely what you'd like to accomplish. Then people can review them
and make suggestions for improvements or changes. I personally find it
rewarding to do so even if my patches aren't excepted in the end. I
always learn something, and the code is archived for those that want to
play with it.
josh
next prev parent reply other threads:[~2007-12-12 14:36 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 [this message]
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
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=20071212083639.337f3049@weaponx \
--to=jwboyer@linux.vnet.ibm.com \
--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