From: "Jörn Engel" <joern@lazybastard.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
Pierre Ossman <drzeus-mmc@drzeus.cx>
Subject: Re: [RFC] MTD driver for MMC cards
Date: Mon, 16 Apr 2007 02:31:48 +0200 [thread overview]
Message-ID: <20070416003148.GA23559@lazybastard.org> (raw)
In-Reply-To: <200704160133.18597.arnd@arndb.de>
On Mon, 16 April 2007 01:33:17 +0200, Arnd Bergmann wrote:
>
> There is also still some need for performance testing. Jörn
> brought up the point that if a specific card can't have multiple
> open erase block simulateously, it's rather pointless for
> logfs. It might still be useful to use jffs2 on those cards,
> because IFAIK that only writes to one erase block at any
> time.
This appears to be a problem for practically all consumer-available
flash media. They spend a lot of effort trying to hide any flash
properties from their users. And while this is a decent strategy for
FAT, ext3, ntfs and similar, it is actually very inefficient for a flash
filesystem.
After talking to several manufacturers, most seemed to be fairly
open-minded towards supporting an alternate interface with raw flash
access. So much for the good news. Bad news is that such an elternate
interface still needs to be defined.
Jörn
--
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon
prev parent reply other threads:[~2007-04-16 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 13:18 [RFC] MTD driver for MMC cards Arnd Bergmann
2006-12-31 12:32 ` Pierre Ossman
2006-12-31 17:40 ` Matthieu CASTET
2007-01-01 22:22 ` Arnd Bergmann
2007-01-02 0:08 ` David Woodhouse
2007-01-04 7:42 ` Pierre Ossman
2007-04-15 23:33 ` Arnd Bergmann
2007-04-16 0:31 ` Jörn Engel [this message]
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=20070416003148.GA23559@lazybastard.org \
--to=joern@lazybastard.org \
--cc=arnd@arndb.de \
--cc=drzeus-mmc@drzeus.cx \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox