public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hooanon05@yahoo.co.jp
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: tomas@slax.org, akpm@linux-foundation.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New filesystem for Linux kernel
Date: Tue, 24 Feb 2009 22:18:10 +0900	[thread overview]
Message-ID: <11287.1235481490@jrobl> (raw)
In-Reply-To: <E1Lbvpf-0006fF-Tg@pomaz-ex.szeredi.hu>


Miklos Szeredi:
> I think the biggest problem is too many features.
> 
>    > git diff master...aufs2 | diffstat
>     ...
>     73 files changed, 23527 insertions(+), 7 deletions(-)
>                       ^^^^^^
> This is an unreviewable amount of code, it would make AUFS one of the
> biggest filesystems on linux.
> 
> The first step would be to separate out the very core functionality,
> which should be a couple thousands of lines max.  And when that has
> been accepted and stabilised, then you can start adding fancy
> features.

I have to admit aufs is big, but actually, as I wrote in the documents,
aufs2 has already dropped several features. And I believe it is the core
feature set. If aufs2 drops some more features, then both of users and
reviewers will say it doesn't work in this case, in that case. I don't
think you would like to review such unusable code in real world.
For those who wants to begin with aufs2 principle (or basic
architecture), I described and posted these documents.

Actually ocfs2 and xfs are much bigger.
If they have been reviewed, I'd ask you to review aufs2 too.
$ cd linux/fs
$ for i in *; do test -d $i && echo -n $i && find $i -type f | xargs wc -l | tail -1; done | tr -s '[[:blank:]]' | sort -n -k 2 | tail
nfs 30363 total
ntfs 31346 total
jfs 33056 total
cifs 34059 total
ubifs 34721 total
btrfs 43417 total
aufs 46325 total
nls 54855 total
ocfs2 71294 total
xfs 102144 total


J. R. Okajima

  reply	other threads:[~2009-02-24 13:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23  7:31 [RFC 0/8] Aufs2 documents hooanon05
2009-02-23  7:33 ` [RFC 1/8] Aufs2: introduction hooanon05
2009-02-23  7:34 ` [RFC 2/8] Aufs2: structure hooanon05
2009-02-23  9:13   ` Tomas M
2009-02-23  9:22     ` Tomas M
2009-02-24  8:13       ` New filesystem for Linux kernel Tomas M
2009-02-24 11:52         ` Miklos Szeredi
2009-02-24 13:18           ` hooanon05 [this message]
2009-02-24 13:45             ` Tarkan Erimer
2009-02-24 13:57               ` hooanon05
2009-02-24 14:16                 ` Tarkan Erimer
2009-02-24 14:50             ` Miklos Szeredi
2009-02-24 16:26               ` hooanon05
2009-02-25 10:28                 ` Miklos Szeredi
2009-02-26  4:09                   ` hooanon05
2009-02-26  5:51               ` hooanon05
2009-02-26  5:55                 ` hooanon05
2009-02-24 14:15         ` Theodore Tso
2009-02-24 15:18           ` David P. Quigley
2009-02-24 15:41             ` hooanon05
2009-02-25 15:53               ` David P. Quigley
2009-02-26  4:21                 ` hooanon05
2009-02-25  7:31             ` Tomas M
2009-02-25  9:33               ` David Newall
2009-02-25  8:12           ` Tomas M
2009-02-26 14:31           ` Amit Kucheria
2009-02-23 14:23     ` [RFC 2/8] Aufs2: structure hooanon05
2009-02-23  7:35 ` [RFC 3/8] Aufs2: lookup hooanon05
2009-02-23  7:36 ` [RFC 4/8] Aufs2: branch hooanon05
2009-02-23  7:36 ` [RFC 5/8] Aufs2: wbr_policy hooanon05
2009-02-23  7:37 ` [RFC 6/8] Aufs2: fmode_exec hooanon05
2009-02-23  7:37 ` [RFC 7/8] Aufs2: mmap hooanon05
2009-02-23  9:18   ` Tomas M
2009-02-23 14:39     ` hooanon05
2009-02-23  7:38 ` [RFC 8/8] Aufs2: plan hooanon05
2009-02-25 17:50 ` [RFC 0/8] Aufs2 documents David P. Quigley
2009-02-25 19:07   ` Matthew Wilcox
2009-02-26  4:54   ` hooanon05
2009-02-26 17:20     ` David P. Quigley
2009-02-27 14:27       ` hooanon05
2009-02-27 18:17         ` David P. Quigley
2009-02-28  8:04           ` hooanon05

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=11287.1235481490@jrobl \
    --to=hooanon05@yahoo.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=tomas@slax.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