public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityuckiy <dedekind@oktetlabs.ru>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: NAND pages cache?
Date: Mon, 15 Nov 2004 12:43:43 +0300	[thread overview]
Message-ID: <41987A4F.6090400@oktetlabs.ru> (raw)
In-Reply-To: <1100510529.5074.119.camel@thomas>

Thomas Gleixner wrote:
> On Mon, 2004-11-15 at 08:49 +0000, David Woodhouse wrote:
> 
>>On Mon, 2004-11-15 at 11:49 +0300, Artem Bityuckiy wrote:
>>
>>>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.
>>>
>>>I don not know is it good to do this only in JFFS2 or on the MTD NAND layer?
>>
>>I thought we already did this in the MTD NAND layer, since we had to
>>read whole pages there to do ECC anyway. Thomas?
> 
> 
> We do caching only if a page is read partially. If we read a full page
> we read directly into the fs buffer.
> 
> The partial reads happen when we read nodes. The full page reads happen
> when we read data. That's sufficient and captures most of the double
> reads on the same page.
> 
> tglx
Hmm, It seems I do not know something about MTD. I thought it *always* 
reads whole
pages in orger to always check ECC... I'll see this more close.

Ok, thanks for comment.

-- 
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  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15  8:49 NAND pages cache? Artem Bityuckiy
2004-11-15  8:49 ` David Woodhouse
2004-11-15  9:22   ` Thomas Gleixner
2004-11-15  9:43     ` Artem Bityuckiy [this message]
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=41987A4F.6090400@oktetlabs.ru \
    --to=dedekind@oktetlabs.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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