From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761536AbYEHN0t (ORCPT ); Thu, 8 May 2008 09:26:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754228AbYEHN0k (ORCPT ); Thu, 8 May 2008 09:26:40 -0400 Received: from rtr.ca ([76.10.145.34]:3799 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753885AbYEHN0i (ORCPT ); Thu, 8 May 2008 09:26:38 -0400 Message-ID: <4822FF8D.7020805@rtr.ca> Date: Thu, 08 May 2008 09:26:37 -0400 From: Mark Lord Organization: Real-Time Remedies Inc. User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: Bart Van Assche Cc: =?UTF-8?B?U3TDqXBoYW5lIEFOQ0VMT1Q=?= , Helge Hafting , Tomasz Chmielewski , LKML , YSadgat1@gcte.com, linux-os@analogic.com, Alan , Linux IDE , Jeff Woods Subject: Re: Compact Flash Question References: <48215673.3060201@wpkg.org> <48216039.3070001@wpkg.org> <4821A12F.2020800@aitel.hist.no> <4821C462.2000108@free.fr> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Bart Van Assche wrote: > On Wed, May 7, 2008 at 5:01 PM, Stéphane ANCELOT wrote: >> we use silicon systems CF with wear leveling inside , we write a few >> kb data back each 1/4 h on it.(log /tmp files are redirected to ram) > > Silicon Systems CompactFlashes are the among the most reliable > CompactFlashes I have used in embedded devices. See also > http://www.siliconsystems.com/silicondrive/whitepapers/SSWP03-Endurance-R.pdf > for a whitepaper that explains their wear leveling and error > correction algorithms. Furthermore, Silicon Systems has a technology > called SiSMART that allows to monitor by how far the CompactFlash is > worn out, such that it can be monitored whether or not it is time to > replace the CompactFlash. (Note: I am not affiliated in any way to > Silicon Systems.) .. Mmm.. according to that document, the "dynamic wear leveling" devices might benefit from having Linux issue CF-Erase commands to unallocated sectors, so that the onboard CF controller can then add those sectors to the wear-leveling rotation scheme. There was discussion at LSF'08 about possible filesystem hooks that could be used for this (and other) purposes when deleting files. Cheers