From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Bart Van Assche <bart.vanassche@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
YSadgat1@gcte.com, linux-os@analogic.com,
Alan <alan@lxorguk.ukuu.org.uk>,
Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: Compact Flash Question
Date: Wed, 07 May 2008 14:31:43 +0200 [thread overview]
Message-ID: <4821A12F.2020800@aitel.hist.no> (raw)
In-Reply-To: <48216039.3070001@wpkg.org>
Tomasz Chmielewski wrote:
>
> How does it work, then?
> How can it do wear levelling over the whole CF if some (or most) area
> of CF is already used by our precious data/metadata?
> It would have to know the areas where no data is stored, but it
> contradicts the CF <-> filesystem separation.
It don't necessarily need to know. It can swap two used blocks, one
often-used and one
rarely-used. That way the rarely-used block is rewriten over the
previously busy
block, and the busy block is moved to the rarely used area that isn't worn.
This implies an extra write whenever a busy block is moved. Don't know if
anybody do this, but the technique is simple enough.
CF-filesystem separation is necessary, for they can't know in advance what
filesystem or partitioning scheme will be used. (I have ext3 on CF, for
example...)
Helge Hafting
next prev parent reply other threads:[~2008-05-07 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48215673.3060201@wpkg.org>
[not found] ` <e2e108260805070044v42f596bbj39c5b52b6f0a096@mail.gmail.com>
2008-05-07 7:54 ` Compact Flash Question Tomasz Chmielewski
2008-05-07 7:58 ` Bart Van Assche
2008-05-07 12:31 ` Helge Hafting [this message]
2008-05-07 15:01 ` Stéphane ANCELOT
2008-05-07 16:46 ` Bart Van Assche
2008-05-08 13:26 ` Mark Lord
2008-05-08 14:27 ` Lennart Sorensen
2008-05-08 14:59 ` Willy Tarreau
2008-05-07 7:27 Tomasz Chmielewski
-- strict thread matches above, loose matches on Subject: below --
2008-05-06 21:59 Yigal Sadgat
2008-05-06 22:09 ` Alan Cox
2008-05-13 17:13 ` Yigal Sadgat
2008-05-06 22:22 ` linux-os (Dick Johnson)
2008-05-07 6:15 ` Bart Van Assche
2008-05-07 7:39 ` Alan Cox
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=4821A12F.2020800@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=YSadgat1@gcte.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bart.vanassche@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mangoo@wpkg.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;
as well as URLs for NNTP newsgroup(s).