From: Mark Lord <liml@rtr.ca>
To: Lionel Bouton <lionel-subscription@bouton.name>
Cc: Erik Slagter <erik@slagter.name>, linux-ide@vger.kernel.org
Subject: Re: USB-Storage, slow speed with sync option
Date: Wed, 14 Sep 2005 17:38:36 -0400 [thread overview]
Message-ID: <4328985C.4000207@rtr.ca> (raw)
In-Reply-To: <432843E5.1060209@bouton.name>
Lionel Bouton wrote:
> Mark Lord wrote the following on 14.09.2005 17:26 :
>> These flash sticks, along with CF and SD cards, all include
>> built-in controllers that do automatic wear-leveling.
>
> Do they all have such controllers now? Last time I checked, low quality
> parts didn't have them and it wasn't easy to verify which ones did.
Pretty much all of them use NAND flash, which comes with 1-3%
bad blocks from the factory. So the onboard controllers already
have to deal with *that* issue, and the same remapping logic is
normally extended to allow them to do wear leveling as well.
Wear leveling is imperfect, in that they devices can only include
sectors *known* by the *device* to be inactive, so as files are
written and deleted many sectors are removed from the wear rotation
until the next time they are logically rewritten (or until a CFA ERASE
command, which Linux never does. Sad.).
Cannot say for sure whether 100% of controllers are adequately intelligent,
but that kind of control logic is pretty pervasive these days.
It would be a very rare device indeed that lacks it.
Cheers
next prev parent reply other threads:[~2005-09-14 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 0:53 USB-Storage, slow speed with sync option Stefan
2005-09-14 9:31 ` Erik Slagter
2005-09-14 10:27 ` Stefan
2005-09-14 10:33 ` Erik Slagter
2005-09-14 10:43 ` Stefan
2005-09-14 12:45 ` Lionel Bouton
2005-09-14 12:51 ` Erik Slagter
[not found] ` <87f94c37050914055852ff4789@mail.gmail.com>
2005-09-14 13:04 ` Erik Slagter
2005-09-14 15:26 ` Mark Lord
2005-09-14 15:38 ` Lionel Bouton
2005-09-14 21:38 ` Mark Lord [this message]
2005-09-14 13:37 ` Stefan
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=4328985C.4000207@rtr.ca \
--to=liml@rtr.ca \
--cc=erik@slagter.name \
--cc=linux-ide@vger.kernel.org \
--cc=lionel-subscription@bouton.name \
/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).