linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: Artem Bityutskiy <dedekind@yandex.ru>,
	linux-fsdevel@vger.kernel.org,
	HIBLOT Jean-Jacques <jjhiblot@adeneo.adetelgroup.com>,
	Gregory CLEMENT <gclement@adeneo.adetelgroup.com>,
	linux-mtd@lists.infradead.org
Subject: Re: Request for review: NandFS
Date: Sat, 7 Feb 2009 12:27:30 +0100	[thread overview]
Message-ID: <71cd59b00902070327u2185377r5735cdd1a68249b8@mail.gmail.com> (raw)
In-Reply-To: <498C40A2.8050100@billgatliff.com>

>> Please, think about joining us instead :-)
>>
>
> Of course, if NandFS is better than UBI/UBIFS, then maybe you should think
> about joining him instead!  :)

Yep, I think you should do that ! :)

Seriously, NandFS may not be scalable, but with checkpoints and
writeback it'll should get better performances than JFFS/YAFFS.
And as it only use mtd, it should be more easily portable to something
else that linux.

But I know that we now need scalable solutions, and it's why I work on
another project ( http://uffs.org/ ). What we are trying to do with
that is totaly different. We will try to do something portable (linux,
windows, fuse (for MacOSX and *BSD)). And more important we wan't to
make it work on raw NAND, *and* on block devices based on NAND. For
that we've got EBM, which is very similar to UBI (and uses UBI on
Linux) to talk to raw NAND or block devices. You may look at
http://uffs.org/pages/documentation .
For the core filesystem, we may make something new or use a modified
version of UBIFS (in this case, the project may be re-named).
Anyway, by working on UFFS, we will contribute to UBI/UBIFS and UBI2
(ebm on block devices will look like UBI2).


-- 
Corentin Chary
http://xf.iksaif.net

      reply	other threads:[~2009-02-07 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 12:27 Request for review: NandFS Corentin Chary
2009-02-06  7:50 ` Artem Bityutskiy
2009-02-06 13:52   ` Bill Gatliff
2009-02-07 11:27     ` Corentin Chary [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=71cd59b00902070327u2185377r5735cdd1a68249b8@mail.gmail.com \
    --to=corentin.chary@gmail.com \
    --cc=bgat@billgatliff.com \
    --cc=dedekind@yandex.ru \
    --cc=gclement@adeneo.adetelgroup.com \
    --cc=jjhiblot@adeneo.adetelgroup.com \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).