From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Tomasz Chmielewski" <mangoo@wpkg.org>
Cc: 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, 7 May 2008 09:58:56 +0200 [thread overview]
Message-ID: <e2e108260805070058p476901f5ta4c38e99e1421eec@mail.gmail.com> (raw)
In-Reply-To: <48216039.3070001@wpkg.org>
On Wed, May 7, 2008 at 9:54 AM, Tomasz Chmielewski <mangoo@wpkg.org> 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.
The wear leveling algorithm even works if the CompactFlash controller
has no knowledge of the sectors on which filesystem data is stored.
All that is needed is some spare space on the CompactFlash that is not
made visible through the IDE interface, a controller that is able to
remap sectors and that stores this mapping persistently.
Bart.
next prev parent reply other threads:[~2008-05-07 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 7:12 Tomasz Chmielewski
2008-05-07 7:44 ` Bart Van Assche
2008-05-07 7:54 ` Tomasz Chmielewski
2008-05-07 7:58 ` Bart Van Assche [this message]
2008-05-07 12:31 ` Helge Hafting
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 14:53 ` Lennart Sorensen
-- 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=e2e108260805070058p476901f5ta4c38e99e1421eec@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=YSadgat1@gcte.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®