Hans,
I support Alan's position relative to the journalling issues. You
should to. None of us have been excluded from providing input from this
process, and it's very clear that Alan is trying to balance all the
requirements and do the right thing for Linux, and your wonderful
ReiserFS. Let's give what he proposes a chance to work, and be
supportive. It's very clear he is taking all of our needs very
seriously and attempting to provide the best path possible for the
evolution of Linux.
What you have done is very good for Linux, and everyone recognizes
this. I applaud your efforts and cleverness. But cut Alan some slack,
having a general mathod for journalling would be a great addition, and
Stephen Tweedie is a very competent architect, no doubt his journalling
stuff will be very good.
Very Truly Yours,
:-)
Jeff
Hans Reiser wrote:
>
> Alan Cox wrote:
> >
> > > fs
> > > --
> > > W Merge ext3
> > > W Merge ReiserFS
> > W Merge XFS
> > W Merge NWFS
> >
> > (All four depend in part on putting the right core journal layer there for
> > them all to use)
>
> This is just a RedHat bureaucratic excuse to delay reiserfs. Tweedie has long
> suggested that we should use his journaling code, and that his code should form
> some sort of standard journaling layer. The only problem with that is that he
> showed no interest in making it work for reiserfs, or in tuning it for reiserfs,
> or doing anything else for any FS other than ext2. We have working journaling
> code, and yours is bad enough that you tell us it is horribly unfair to
> benchmark against it! So you suggest that we wait until you have something that
> will allow us to use your code!? If you want us to use your code, show the
> code, stop promising the code, and stop telling us to wait for it rather than
> using our benchmarkably better code. Prove that your code can work for reiserfs
> as fast as what we use today. The fact is, Chris Mason kicked your asses
> performance wise and now you want to employ some journaling standardization
> process to stall your competitors that you can't program as well as.
>
> Why don't you help us with ReiserFS instead of standing in the way of people
> trying to program?
>
> Journaling should no more be held in common than any other aspect of the
> filesystem. Nor should it be standardized for filesystems that don't find it to
> be what they want. Just because journaling in reiserfs is working and debugged
> and in code freeze for 2.4 doesn't mean that we are more than halfway down the
> path of what we are going to do in journaling. We will be doing wandering logs,
> and journaling in ReiserFS has another 18 months of DEEP innovations planned for
> it. Standardization bureaucrats should stay out of the way, we need to code.
>
> Hans
>
> PS
>
> If you want to use our journaling code, you can.... but I rather doubt that was
> what you had in mind.... and I don't want our filesystem to wait for you to
> catch up to it. I really don't understand why RedHat clings so hard to an old
> technology FS. New technologies come along all the time, why not embrace them?
> Your people ARE talented, and could contribute so much if they weren't standing
> in the way. Ext2 was a great thing, and it was the best FS in its time, but the
> time has come to let it go....
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:22 EST