[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2e108260805070058p476901f5ta4c38e99e1421eec@mail.gmail.com>
Date: Wed, 7 May 2008 09:58:56 +0200
From: "Bart Van Assche" <bart.vanassche@...il.com>
To: "Tomasz Chmielewski" <mangoo@...g.org>
Cc: LKML <linux-kernel@...r.kernel.org>, YSadgat1@...e.com,
linux-os@...logic.com, Alan <alan@...rguk.ukuu.org.uk>,
"Linux IDE" <linux-ide@...r.kernel.org>
Subject: Re: Compact Flash Question
On Wed, May 7, 2008 at 9:54 AM, Tomasz Chmielewski <mangoo@...g.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists