From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org, Kevin Vigor <kevin@realmsys.com>
Subject: Re: [PATCH] avoid unnnecessary mtd read when read can be satisfied by write buffer
Date: Thu, 01 Jun 2006 16:05:07 +0100 [thread overview]
Message-ID: <1149174307.10909.3.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060601144902.GC15216@wohnheim.fh-wedel.de>
On Thu, 2006-06-01 at 16:49 +0200, Jörn Engel wrote:
> One of the observations was that a lot of flash is being read multiple
> times. Reads on NAND happen in page granularity, so first we have to
> read pretty much everything during scan, later again when accessing
> the actual files. There is some room for savings, as RAM is faster
> than flash even in the real world.
My point is that for any given problem, raw caching of flash is not the
answer -- something more cunning is going to be better.
The specific cases of dirents and symlinks I already talked about. Any
other time we keep reading the same bit of flash over and over again is
also a problem. The one you mention is fixed by using eraseblock
summary.
I need to finish what I was doing yesterday, which halves the amount of
space taken by summaries. We should probably also remove the dependency
on EXPERIMENTAL.
--
dwmw2
next prev parent reply other threads:[~2006-06-01 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 21:50 [PATCH] avoid unnnecessary mtd read when read can be satisfied by write buffer Kevin Vigor
2006-06-01 14:32 ` Jörn Engel
2006-06-01 14:39 ` David Woodhouse
2006-06-01 14:49 ` Jörn Engel
2006-06-01 15:05 ` David Woodhouse [this message]
2006-06-01 15:27 ` Jörn Engel
[not found] <85257180.00537972.00@pine.cspi.com>
2006-06-01 16:10 ` Kevin Vigor
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=1149174307.10909.3.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=kevin@realmsys.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