From: Richard Miller <rm@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] disk/^(mbr format fdisk prep)
Date: Thu, 13 May 2004 09:18:51 +0100 [thread overview]
Message-ID: <5061a8376a19eedb43283f53c0b2b46a@hamnavoe.com> (raw)
In-Reply-To: <2a2f13faee87856b7686b122a9cb1830@orthanc.cc.titech.ac.jp>
Many (most?) flash devices do "wear-levelling": blocks which are being
frequently rewritten will be periodically remapped by the firmware or
driver so that erase activity is spread evenly across all blocks. So
it is the average number of writes per block which determines the
device life expectancy, not the peak number.
next prev parent reply other threads:[~2004-05-13 8:18 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 2:57 YAMANASHI Takeshi
2004-05-13 3:20 ` Kenji Okamoto
2004-05-13 3:22 ` Kenji Okamoto
2004-05-13 8:18 ` Richard Miller [this message]
2004-05-13 8:34 ` lucio
2004-05-13 8:52 ` Richard Miller
2004-05-13 13:52 ` ron minnich
2004-05-13 17:35 ` Joel Salomon
2004-05-13 18:43 ` boyd, rounin
2004-05-13 19:14 ` matt
2004-05-13 19:02 ` Nigel Roles
2004-05-13 19:18 ` boyd, rounin
2004-05-13 20:25 ` Joel Salomon
2004-05-13 20:47 ` boyd, rounin
2004-05-13 23:44 ` Russ Cox
2004-05-14 0:15 ` boyd, rounin
2004-05-14 0:24 ` boyd, rounin
2004-05-14 9:56 ` a
2004-05-13 22:18 ` Charles Forsyth
2004-05-13 22:31 ` boyd, rounin
2004-05-13 22:39 ` Charles Forsyth
2004-05-13 22:41 ` boyd, rounin
2004-05-13 22:56 ` Charles Forsyth
2004-05-13 23:01 ` boyd, rounin
2004-05-14 3:29 ` ron minnich
2004-05-14 3:30 ` boyd, rounin
2004-05-13 22:51 ` Joel Salomon
2004-05-13 23:35 ` boyd, rounin
2004-05-13 19:51 ` ron minnich
2004-05-13 22:40 ` Charles Forsyth
2004-05-13 9:16 ` Charles Forsyth
2004-05-13 9:22 ` Kenji Okamoto
2004-05-13 12:45 ` dvd
2004-05-13 14:11 ` Charles Forsyth
2004-05-13 14:19 ` dvd
2004-05-13 17:12 ` Charles Forsyth
2004-05-14 1:03 ` Kenji Okamoto
2004-05-14 3:13 ` dvd
2004-05-14 3:24 ` Kenji Okamoto
2004-05-14 8:59 ` David Tolpin
2004-05-14 9:17 ` Kenji Okamoto
2004-05-15 8:23 ` Adrian Tritschler
2004-05-15 12:05 ` boyd, rounin
2004-05-17 1:48 ` Kenji Okamoto
2004-05-14 16:31 ` Joel Salomon
2004-05-14 16:53 ` a
2004-05-14 17:11 ` Sape Mullender
2004-05-14 17:22 ` andrey mirtchovski
2004-05-14 19:36 ` ron minnich
2004-05-14 19:52 ` andrey mirtchovski
2004-05-14 18:12 ` a
2004-05-14 17:21 ` dvd
2004-05-14 18:14 ` a
2004-05-14 10:01 ` a
2004-05-14 22:31 ` Geoff Collyer
[not found] <06d501c4350f$006a13f0$265d7d50@SOMA>
2004-05-10 4:54 ` lucio
[not found] <ee9e417a040508081247498d73@mail.gmail.com>
2004-05-10 4:43 ` lucio
-- strict thread matches above, loose matches on Subject: below --
2004-05-08 8:53 lucio
2004-05-08 9:08 ` Charles Forsyth
2004-05-08 9:30 ` Kenji Okamoto
2004-05-08 9:37 ` Kenji Okamoto
2004-05-08 9:41 ` lucio
2004-05-08 9:50 ` lucio
2004-05-08 11:38 ` Charles Forsyth
2004-05-09 5:50 ` Geoff Collyer
2004-05-09 6:03 ` Geoff Collyer
2004-05-10 0:59 ` Kenji Okamoto
2004-05-10 5:10 ` lucio
2004-05-10 5:25 ` Kenji Okamoto
2004-05-10 5:30 ` lucio
2004-05-13 2:36 ` Kenji Okamoto
2004-05-13 2:42 ` boyd, rounin
2004-05-13 2:50 ` Kenji Okamoto
2004-05-10 5:08 ` lucio
2004-05-08 9:56 ` lucio
2004-05-10 9:09 ` Fco.J.Ballesteros
2004-05-10 9:17 ` lucio
2004-05-08 9:58 ` Richard Miller
2004-05-08 10:02 ` lucio
2004-05-08 10:47 ` Richard Miller
2004-05-08 11:13 ` lucio
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=5061a8376a19eedb43283f53c0b2b46a@hamnavoe.com \
--to=rm@hamnavoe.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).