From: David Woodhouse <dwmw2@infradead.org>
To: Davide CASCONE <davide.cascone@st.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 mounting performance improvement
Date: Tue, 20 Jun 2006 09:47:54 +0100 [thread overview]
Message-ID: <1150793274.3176.469.camel@pmac.infradead.org> (raw)
In-Reply-To: <000601c69443$1c7de450$253682a4@nap.st.com>
On Tue, 2006-06-20 at 10:25 +0200, Davide CASCONE wrote:
>
> It seems that during the JFFS2 mounting, the file system uses the
> function cfi_intelext_point (in jffs2_scan_medium function) to point
> to the flash memory. This function refers to the flash memory using
> the virtual address (map->virt). But if the flash is cached and the
> burst mode is enabled, it should be better to refer to the flash with
> the address map->cached (in the same way of cfi_intelext_read
> function, that calls the map_copy_from function, in which there is a
> check to verify if the flash is cached). This improves in a
> considerable way the performance during the mounting phase, reducing
> the mounting time.
> What do you think about? Do you agree with me?
Yes. As long as you handle the cache invalidation where appropriate, you
should definitely use the cached address for the 'point' function.
> Do you know if there are other points in JFFS2 code that uses the
> virtual address map->virt instead of map->cached.
JFFS2 wouldn't touch that directly. It's down to the chip driver. JFFS2
just uses the read() and point() methods (during scan), so I think the
answer would be 'no'.
--
dwmw2
prev parent reply other threads:[~2006-06-20 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 8:25 JFFS2 mounting performance improvement Davide CASCONE
2006-06-20 8:36 ` Balaji
2006-06-20 8:47 ` David Woodhouse [this message]
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=1150793274.3176.469.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=davide.cascone@st.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