linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christer Weinigel <christer@weinigel.se>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: jim owens <jowens@hp.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Tuning for Compact Flash
Date: Tue, 30 Sep 2008 01:11:49 +0200	[thread overview]
Message-ID: <48E160B5.1090502@weinigel.se> (raw)
In-Reply-To: <yq11vz3f0bm.fsf@sermon.lab.mkp.net>

Martin K. Petersen wrote:

>>>>>> "Christer" == Christer Weinigel <christer@weinigel.se> writes:
> 
> Christer> Of course it won't behave like a hard drive, but it would be
> Christer> nice if there was a file system with performance that didn't
> Christer> suck as badly on a compact flash.
> 
> Well, you are limited by the capabilities of the FTL.  And as far as
> CF goes the FTL is usually pretty braindead.


Yeah, I wish some flash manufacturer would do the right thing and just 
stick some NAND chips and some PCI/PCIe glue on a CardBus/ExpressCard. 
Something that allows a Linux driver to talk directly to the flash chips 
and then a simple DMA engine to do bus mastering block transfers to and 
from memory.  We could then run yaffs or whatever we wanted on it with 
no translation layers at all in between.

> But as far as CF is concerned I have tested many and not found a
> single one that is suitable for a regular (random) filesystem write
> workload.  To the extent that for embedded devices I ended up putting
> a root filesystem tarball on the CF and unpacking it into ramfs during
> boot.
> 
> And just to give you an idea: I'm getting two orders of magnitude less
> random write ops on a (high-performance) CF than on a flash SSD from
> the same vendor.  In both cases with I/O aligned to the flash page
> boundary.

That sounds just horrid.  Oh well, I won't have much choice when my hard 
drive dies, drives in this form factor are not manufactured any more and 
the only thing that will fit into the slot is a Compact Flash card or 
maybe with some hacking a USB drive.  :-)

  /Christer

  reply	other threads:[~2008-09-29 23:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-27 12:54 Tuning for Compact Flash Christer Weinigel
2008-09-28 15:28 ` jim owens
2008-09-29  6:54   ` Artem Bityutskiy
2008-09-29 12:23   ` Christer Weinigel
2008-09-29 15:17     ` Martin K. Petersen
2008-09-29 23:11       ` Christer Weinigel [this message]
2008-10-02 16:40         ` Chuck Lever

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=48E160B5.1090502@weinigel.se \
    --to=christer@weinigel.se \
    --cc=jowens@hp.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /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).