Message-ID: <462E17AF.7090604@namesys.com>
Date:	Tue, 24 Apr 2007 18:43:59 +0400
From:	Edward Shishkin <edward@...esys.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	"Vladimir V. Saveliev" <vs@...esys.com>,
	Andi Kleen <andi@...stfloor.org>
CC:	Alex Zarochentsev <zam@...esys.com>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Eric Hopper <hopper@...ifarious.org>, Lex Lyamin <flx@....ru>,
	William Heimbigner <icxcnika@....tar.cc>,
	Rik van Riel <riel@...hat.com>,
	Xu CanHao <xucanhao@...il.com>
Subject: Re: Question about Reiser4

Hello everyone.

>Begin forwarded message:
>
>Date: 23 Apr 2007 21:05:13 +0200
>From: Andi Kleen <andi@...stfloor.org>
>To: Andrew Morton <akpm@...ux-foundation.org>
>Cc: Eric Hopper <hopper@...ifarious.org>, linux-kernel@...r.kernel.org
>Subject: Re: Question about Reiser4
>
>
>Andrew Morton <akpm@...ux-foundation.org> writes:
>  
>
>>To get it unstuck we'd need a general push, get people looking at and testing
>>the code, get the vendors to have a serious think about it, etc.  We could do
>>that - it'd require that the namesys people (and I) start making threatening
>>noises about merging it, I guess.
>>    
>>
>
>My impression was that a lot of negative discussion came out of some of the
>user interface inventions in r4 (like sys_reiser4 and the
>new incompatible EA interface). 
>
>  
>

sys_reiser4 and metas interface were removed (current -mm stuff
doesn't contain them).

>I guess a good strategy to get it going would be to extract just
>a "core reiser4" out of it that is just a file system without
>any new interfaces like this.
>
>  
>

I think that current reiser4 is exactly that "core", which responds solely
to VFS. The popular opinion that plugins make more sense in the VFS
is a great delusion, as plugins are entities related to reiser4 disk 
layouts.
There are many aspects where plugin architecture is useful, I tried to
describe one of them -- backward compatibility that was got with
minimal efforts: http://dev.namesys.com/Version4.X.Y
If this needs more comments, then we will proceed the documentation.

>I would expect that reviewing that would be much smoother
>because people could actually concentrate on the technical details.
>
>-Andi
>
>  
>

Other comments:

1. Why Namesys developers aren't presently asking for inclusion?

Because there are unaddressed items in this todo list:
http://pub.namesys.com/Reiser4/ToDo
The main issues here are xattrs and support for blocksize != pagesize.
I think that adding xattrs will take ~1 month of full-time working.
Not sure about blocksize support. Also, the statement about "main
issues" may be too optimistic. Let's try to estimate..

2. Who will maintain this?

Currently there are two namesys employees working mostly on
enthusiasm. Divide them into 2 file systems, plus many people who
really help with fixing problems.

So we need to estimate how dramatic the situation with reiser4 is
(experts are welcome). In the worst case (no funding for this in the
perspective) I hope to devote ~25% of my working time to this
project. Vladimir might want to add something here, but he is sick
for now. By the way, he has its own opinion what part of current
reiser4 should go to mainline (separating tail's support (which
makes things complicated) as special incremental update available
on our website).

Thanks,
Edward.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists