All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: linux-mtd@lists.infradead.org
Subject: Writing frequently to NAND - wearing, caching?
Date: Thu, 03 Feb 2005 10:31:42 +0100	[thread overview]
Message-ID: <ctsr0r$94m$1@sea.gmane.org> (raw)

Hi there,

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?
I know this is a very diffuse question, but hopefully you get my drift.

BR,
  Martin Egholm

             reply	other threads:[~2005-02-03  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  9:31 Martin Egholm Nielsen [this message]
2005-02-06 22:14 ` Writing frequently to NAND - wearing, caching? Charles Manning
2005-02-07  8:33   ` Martin Egholm Nielsen
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='ctsr0r$94m$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.