From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: "ext Johnson, Charles F" <charles.f.johnson@intel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS - Current Status?
Date: Fri, 26 Oct 2007 10:22:08 +0300 [thread overview]
Message-ID: <472195A0.90500@nokia.com> (raw)
In-Reply-To: <B1EDF20A6EAAD74EA65E46F774F1784502B9DBE4@orsmsx413.amr.corp.intel.com>
ext Johnson, Charles F wrote:
> Just curious on what the current state of UBIFS ??
UBIFS is still under development. It's state could be described as
testable meaning that all file system operations are implemented
and seem to work.
We are currently working on two areas: 1) recovery from unclean unmounts,
and 2) what we call "budgeting", the ability to know if everything in
VFS caches will actually fit on the flash. Other outstanding items are:
support for different compression schemes (only LZO presently), support
for extended attributes, userspace tools (e.g. mkfs.ubifs).
We hope to have something that could be considered production-ready
some time early next year.
> I'm looking for a solution which could support very large MLC NAND flash
> design. UBIFS+UBI looks like it a good candidate.
While UBIFS is designed to be scalable, UBI scales linearly with the
number of eraseblocks. UBI is probably ok up to MTD's 4GiB limit. Bigger
than that and someone needs to fix MTD's 32-bit size limitation and write
UBI2.
next prev parent reply other threads:[~2007-10-26 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 21:42 UBIFS - Current Status? Johnson, Charles F
2007-10-26 7:22 ` Adrian Hunter [this message]
2007-11-19 9:00 ` 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=472195A0.90500@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=charles.f.johnson@intel.com \
--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