Re: First draft list of 2.3.x "Things to fix"

[Hans Reiser]

While there is a lot of work to be done to do things right, I don't think there
is a
lot of work to put ext3 and ReiserFS into 2.3.  We are working on the port right
now
for ReiserFS, and I don't think we are far away.

If we wait for everything to be right, software never ships....

I think the thing to consider is that we can put journaling into 2.4, and then
niceties
like allocate on flush can be done later in 2.5.

I have some concern that you are suggesting that there should be only one
journaling
coding for both filesystems, and that is not only far away but far from clear to
me.
Chris Mason (ReiserFS journaling code author) may disagree with this, and is
encouraged
to comment.  I'll just note that we envision re-engineering journaling now that
the
current journaling is stable.   Users should use the current journaling, it
should go
into 2.4 because lack of journaling is keeping many users away from Linux, but
journaling is not ready for the ANSI standards process.:-)  Nor is it ready for
sharing
between many filesystems....  We have more than one filesystem, why not more
than one
journaling system?

Hans

Alan Cox wrote:

> > I just came up with something else that'd be great to have in v2.4
> >
> > * ext3 (Depends on whether it's remotely close to something of a beta, at
> > least... (CONFIG_EXPERIMENTAL would be nice here, at least))
>
> There is a lot of work to be done to get the journalling layer nicely arranged to do
> the right things and to do them right for XFS, ext3 and Reiserfs - not 2.4 material
> by any means.
>
> Alan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [e-mail]
> Please read the FAQ at http://www.tux.org/lkml/

--
Get Linux (http://www.kernel.org) plus ReiserFS
 (http://devlinux.org/namesys).  If you sell an OS or
internet appliance, buy a port of ReiserFS!  If you
need customizations and industrial grade support, we sell them.