public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: linux-mtd@lists.infradead.org
Subject: Re: Writing frequently to NAND - wearing, caching?
Date: Mon, 07 Feb 2005 09:33:48 +0100	[thread overview]
Message-ID: <cu7934$irr$1@sea.gmane.org> (raw)
In-Reply-To: <20050206220713.D99FE15504@desire.actrix.co.nz>

Hi,

>>I have an application which may need to write states frequently to my
>>nand-fs in order to have these states in case of powerdown.
>>But I'm a bit concerned about wearing the nand if I write to frequently.

>>So, if I only need to write, say, 100 bytes every second, how often will
>>this actually be flushed to the nand?
>>Is there a maximum commit/flush frequency built in the driver? Or can
>>this be configured?

> It depends on what fs you're using.
> With YAFFS, and I believe JFFS2 too, there is no reason to worry about flash 
> "wearing out".  I have done accelerated lifetime tests on NAND using YAFFS 
> and in one test wrote 130GB to NAND without any data loss, bad blocks 
> happening etc.
Now, that's a lot :-)
I'm using JFFS2 - so hopefully you're right...

> The NAND writes whenever the file system tells it to, so again your question 
> is FS dependent, but all file systems that are NAND-friendly should handle 
> the load you mention with no problems.
And that is JFFS2 - but since it's a journaling fs it must commit the 
journal, as well, every now and then...

// Martin

  reply	other threads:[~2005-02-07  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  9:31 Writing frequently to NAND - wearing, caching? Martin Egholm Nielsen
2005-02-06 22:14 ` Charles Manning
2005-02-07  8:33   ` Martin Egholm Nielsen [this message]
2005-02-07 12:02     ` Estelle HAMMACHE
2005-02-08  0:12     ` Charles Manning
2005-02-09  6:16       ` Aras Vaichas
2005-02-14  8:37         ` Martin Egholm Nielsen

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='cu7934$irr$1@sea.gmane.org' \
    --to=martin@egholm-nielsen.dk \
    --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