linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: "Stéphane ANCELOT" <sancelot@free.fr>,
	"Helge Hafting" <helge.hafting@aitel.hist.no>,
	"Tomasz Chmielewski" <mangoo@wpkg.org>,
	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>,
	"Jeff Woods" <jeff@jeffwoods.us>
Subject: Re: Compact Flash Question
Date: Thu, 08 May 2008 09:26:37 -0400	[thread overview]
Message-ID: <4822FF8D.7020805@rtr.ca> (raw)
In-Reply-To: <e2e108260805070946t63f35e36q6960bdff11fecd8c@mail.gmail.com>

Bart Van Assche wrote:
> On Wed, May 7, 2008 at 5:01 PM, Stéphane ANCELOT <sancelot@free.fr> 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

  reply	other threads:[~2008-05-08 13:26 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
2008-05-07 15:01       ` Stéphane ANCELOT
2008-05-07 16:46         ` Bart Van Assche
2008-05-08 13:26           ` Mark Lord [this message]
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=4822FF8D.7020805@rtr.ca \
    --to=liml@rtr.ca \
    --cc=YSadgat1@gcte.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bart.vanassche@gmail.com \
    --cc=helge.hafting@aitel.hist.no \
    --cc=jeff@jeffwoods.us \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=mangoo@wpkg.org \
    --cc=sancelot@free.fr \
    /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).