public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityuckiy <dedekind@oktetlabs.ru>
To: linux-mtd@lists.infradead.org
Subject: NAND pages cache?
Date: Mon, 15 Nov 2004 11:49:13 +0300	[thread overview]
Message-ID: <41986D89.4060308@oktetlabs.ru> (raw)

Hello,

It is known that MTD always reads/writes in fractions of the whole NAND 
pages. An this is right I believe.

But while working with JFFS2, I have mentioned that very often it reads 
the same page several times consequently. This happens for example, when 
JFFS2 performs Garbage Collection, and there are several small nodes in 
the NAND page. Thus, when JFFS2 reads these nodes, it re-reads the same 
NAND page several times. This is bad.

So, the obvious idea how to avoid this is to introduce something like 
NAND pages cache. The cache will keep several NAND pages which were last 
accessed.

Obviously, this will require at least one more page buffer copy 
operation and, for example, will only decrease the sequential read speed.

So, It is possible to introduce calls like:

nand_read_buffered
nand_read_unbuffered

I don not know is it good to do this only in JFFS2 or on the MTD NAND layer?

Comments?

Thanks.

-- 
Best regards, Artem B. Bityuckiy
Oktet Labs (St. Petersburg), Software Engineer.
+78124286709 (office) +79112449030 (mobile)
E-mail: dedekind@oktetlabs.ru, web: http://www.oktetlabs.ru

             reply	other threads:[~2004-11-15  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15  8:49 Artem Bityuckiy [this message]
2004-11-15  8:49 ` NAND pages cache? David Woodhouse
2004-11-15  9:22   ` Thomas Gleixner
2004-11-15  9:43     ` Artem Bityuckiy
2004-11-15  9:57       ` Thomas Gleixner
2004-11-15 10:07         ` Artem Bityuckiy

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=41986D89.4060308@oktetlabs.ru \
    --to=dedekind@oktetlabs.ru \
    --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