From: payagond@aol.com
To: linux-mtd@lists.infradead.org
Subject: Increasing read request size in JFFS2
Date: Fri, 14 Sep 2007 07:24:21 -0400 [thread overview]
Message-ID: <8C9C4D8EE8B6B02-F08-232@webmail-mf13.sysops.aol.com> (raw)
Hi,
I want to know, whether, we can exploit the fast sequential read
(multiple pages at one go) feature of a nand flash device by existing
JFFS2 code.
read_pages in readahead decides to call either
mapping->a_ops->readpages or mapping->a_ops->readpage
can I implement jffs2_readpages to do so?
The problem I feel is (if I have understood correctly)
To read more pages at one shot, we need to anyway read the
jffs2_raw_inode header first and then calculate the lenth to read, will
it give me more performance than what is existing?
regards
payagond
________________________________________________________________________
Email and AIM finally together. You've gotta check out free AOL Mail! -
http://mail.aol.com
next reply other threads:[~2007-09-14 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 11:24 payagond [this message]
2007-09-14 11:38 ` Increasing read request size in JFFS2 Artem Bityutskiy
2007-09-14 12:50 ` Josh Boyer
2007-09-17 10:26 ` need patch for SST39VF301flash chips Bruno
2007-09-17 11:06 ` Josh Boyer
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=8C9C4D8EE8B6B02-F08-232@webmail-mf13.sysops.aol.com \
--to=payagond@aol.com \
--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