From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christer Weinigel <christer@weinigel.se>
Cc: jim owens <jowens@hp.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Tuning for Compact Flash
Date: Mon, 29 Sep 2008 11:17:49 -0400 [thread overview]
Message-ID: <yq11vz3f0bm.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <48E0C8DA.6090502@weinigel.se> (Christer Weinigel's message of "Mon\, 29 Sep 2008 14\:23\:54 +0200")
>>>>> "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.
Making sure things are properly aligned really helps on "real" SSDs as
well as 4KB hw sector drives. I'm working on some code that exposes
these parameters so we can perform that alignment when creating
filesystems.
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.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2008-09-29 15:18 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 [this message]
2008-09-29 23:11 ` Christer Weinigel
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=yq11vz3f0bm.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=christer@weinigel.se \
--cc=jowens@hp.com \
--cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.