From: Artem Bityutskiy <dedekind@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, Seongsu Lee <senux@senux.com>
Subject: Re: What is ANAND header?
Date: Thu, 25 Jan 2007 17:57:33 +0200 [thread overview]
Message-ID: <1169740653.3721.10.camel@sauron> (raw)
In-Reply-To: <1169739059.3593.84.camel@shinybook.infradead.org>
On Thu, 2007-01-25 at 23:30 +0800, David Woodhouse wrote:
> On Thu, 2007-01-25 at 20:12 +1100, Artem Bityutskiy wrote:
> > On Thu, 2007-01-25 at 15:49 +0900, Seongsu Lee wrote:
> > > Then, is there any technical reason that translation layer
> > > for bare NAND flash memory is *not* exist?
> >
> > Just because it is a damn difficult task.
>
> No it isn't. It's just not an _interesting_ task. A 'normal' file system
> on top of a translation layer is always going to be suboptimal when
> compared to a file system designed to run directly on flash.
Well, FTL is somewhat similar to flash FS in terms of complexity. A
reasonably good FTL is probably not a damn difficult task. But a
scalable FTL where you do not need to scan your device when initializing
it is really difficult.
Of course, FTL will always be slower then flash-oriented FS. But if you
have a very quick HW (like Cafe?) you may end-up with an acceptable
speed - this depends on requirements.
Also, if you teach the FS to inform FTL about blocks that are free -
it'll be much faster.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2007-01-25 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 6:36 What is ANAND header? Seongsu Lee
2007-01-14 17:07 ` Thomas Gleixner
2007-01-24 5:47 ` Seongsu Lee
2007-01-24 12:14 ` Ricard Wanderlöf
2007-01-25 6:49 ` Seongsu Lee
2007-01-25 9:12 ` Artem Bityutskiy
2007-01-25 15:30 ` David Woodhouse
2007-01-25 15:57 ` Artem Bityutskiy [this message]
2007-01-25 16:17 ` David Woodhouse
2007-01-25 16:44 ` Artem Bityutskiy
2007-01-25 16:55 ` David Woodhouse
2007-01-25 17:31 ` Artem Bityutskiy
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=1169740653.3721.10.camel@sauron \
--to=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=senux@senux.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 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.