public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Corentin Chary <corentincj@iksaif.net>
To: linux-mtd@lists.infradead.org
Cc: linux-fsdevel@vger.kernel.org,
	Gregory CLEMENT <gclement@adeneo.adetelgroup.com>,
	HIBLOT Jean-Jacques <jjhiblot@adeneo.adetelgroup.com>
Subject: Request for review: NandFS
Date: Tue, 3 Feb 2009 13:27:59 +0100	[thread overview]
Message-ID: <200902031327.59536.corentincj@iksaif.net> (raw)

Hi,
Here is NandFS, a NAND Flash Filesystem.
NandFS is similar to YAFFS2 (in some ways), but the codebase is much more
cleaner and simpler. And we'll try to go mainline.

Development started at Adeneo (http://www.adeneo-embedded.com/srt/en/home) in 
2007. After a long pause, I re-started to clean the code in october 2008.

With the new UBIFS, we might think than there is no room for another flash 
filesystem. But another GPLed filesystem can't hurt anyone. Some of us may 
have heard some words about UFFS, but this project is in no way related to 
NandFS.

*IMPORTANT*: NandFS is under active development, and can't be considered safe 
or stable !

NandFS aims to be:
- Simple
- Clean
- Ram-Efficient
- Power-Failure-Resistant
- Write-Optimized (write-back + internal caches)
- Wear-Leveling

NandFS work-in-progress:
- writeback and "budgeting"
- kernel-doc

NandFS short term todo:
- (A lot of) Test
- Better locking (no more "Big NandFS Lock")
- checkpoint/summary support
- ram usage optimizations
- xattr support
- acl support

The code can be found at http://git.iksaif.net/

I'm currently working on kernel-doc, but the more important is done.
There is no whitepaper to explain how it works right now, but nandfs.h and 
scan.c explains a lot and they are well commented.

It's all Licenced under GPLv2.

Please post your question/comments/bugs/patches.

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

             reply	other threads:[~2009-02-03 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 12:27 Corentin Chary [this message]
2009-02-06  7:50 ` Request for review: NandFS Artem Bityutskiy
2009-02-06 13:52   ` Bill Gatliff
2009-02-07 11:27     ` Corentin Chary

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=200902031327.59536.corentincj@iksaif.net \
    --to=corentincj@iksaif.net \
    --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