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: Re: Follow-up to wearing / caching question
Date: Mon, 07 Feb 2005 22:36:45 +0100	[thread overview]
Message-ID: <cu8n22$acu$1@sea.gmane.org> (raw)
In-Reply-To: <20050207195209.GC25504@wohnheim.fh-wedel.de>

Hi there,

>> I've been tasked with approximating the lifespan of the flash
>> (JFFS2) filesystem embedded in our products. Is there a best method
>> for calculating the space required for a fixed-size file over a
>> given lifespan? If we want our flash filesystem to be available for
>> an approximate lifespan of 20 years, given the wear-leveling
>> duty-cycle of JFFS2, and an average block endurance of 100k 
>> write/erase cycles, would I need 150% of the file's size? 200%?
>> 1000%?
=== 8< 8< 8< ===
> Another way to look at it is an imaginary 1MiB flash.  You can write
> it 100k times, for a total of 100GiB written to it.  With 600M seconds
> in your expected 20 years, that gives you ~160 Bytes/s average write
> speed.  Not very much.
Then what about the pagesize and corresponding writebuffer - this may 
have an effect, as well, when talking that slow write rates, right?!

> Is that the calculation you were looking for?
I liked it alot - thanks! ;-)

// Martin

  reply	other threads:[~2005-02-07 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 18:51 Follow-up to wearing / caching question Matthew Cole
2005-02-07 19:52 ` Jörn Engel
2005-02-07 21:36   ` Martin Egholm Nielsen [this message]
2005-02-08 15:09     ` Jörn Engel
2005-02-08  0:22   ` Charles Manning
2005-02-08 13:23     ` Jörn Engel

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='cu8n22$acu$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.