From: Hans Reiser <reiser@namesys.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andi Kleen <ak@suse.de>, David Weinehall <david@southpole.se>,
Dax Kelson <dax@gurulabs.com>,
Peter Nelson <pnelson@andrew.cmu.edu>,
linux-kernel <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net, ext3-users@redhat.com,
jfs-discussion@www-124.southbury.usf.ibm.com,
reiserfs-list@namesys.com, linux-xfs@oss.sgi.com
Subject: Re: Desktop Filesystem Benchmarks in 2.6.3
Date: Wed, 03 Mar 2004 11:03:37 +0300 [thread overview]
Message-ID: <40459159.1090501@namesys.com> (raw)
In-Reply-To: <20040303074756.A25861@infradead.org>
Christoph Hellwig wrote:
>On Wed, Mar 03, 2004 at 03:39:26AM +0100, Andi Kleen wrote:
>
>
>>A lot of this is actually optional features the other FS don't have,
>>like support for separate realtime volumes and compat code for old
>>revisions, journaled quotas etc. I think you could
>>relatively easily do a "mini xfs" that would be a lot smaller.
>>
>>
>
>And a whole lot of code to stay somewhat in sync with other codebases..
>
>
>
>
>
What is significant is not the affect of code size on modern
architectures, code size hurts developers as the code becomes very hard
to make deep changes to. It is very important to carefully design your
code to be easy to change. This is why we tossed the V3 code and wrote
V4 from scratch using plugins at every conceivable abstraction layer. I
think V4 will be our last rewrite from scratch because of our plugins,
and because of how easy we find the code to work on now.
I think XFS is going to stagnate over time based on the former
developers who have told me how hard it is to work on the code.
Christoph probably disagrees, and he knows the XFS code far better than
I.;-)
--
Hans
next prev parent reply other threads:[~2004-03-03 8:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 4:46 Desktop Filesystem Benchmarks in 2.6.3 Peter Nelson
2004-03-02 7:23 ` Hans Reiser
2004-03-02 16:34 ` Peter Nelson
2004-03-02 22:33 ` Dax Kelson
2004-03-02 22:47 ` David Weinehall
2004-03-03 1:30 ` Andrew Ho
2004-03-03 1:41 ` David Weinehall
[not found] ` <20040303014115.GP19111@khan.acc.umu.se.suse.lists.linux.kernel>
2004-03-03 2:39 ` Andi Kleen
2004-03-03 7:47 ` Christoph Hellwig
2004-03-03 8:03 ` Hans Reiser [this message]
2004-03-03 8:16 ` Arjan van de Ven
2004-03-03 9:35 ` Hans Reiser
2004-03-03 6:00 ` Robin Rosenberg
2004-03-03 9:43 ` Felipe Alfaro Solana
2004-03-03 9:59 ` Robin Rosenberg
2004-03-03 10:19 ` Felipe Alfaro Solana
2004-03-04 9:28 ` Kristian Köhntopp
2004-03-05 1:59 ` Clemens Schwaighofer
2004-03-03 10:24 ` Mike Gigante
2004-03-03 13:14 ` Felipe Alfaro Solana
2004-03-03 14:16 ` Hans Reiser
2004-03-03 13:42 ` Hans Reiser
2004-03-03 10:13 ` Olaf Frączyk
2004-03-03 13:07 ` Felipe Alfaro Solana
2004-03-04 14:37 ` [Jfs-discussion] " Pascal Gienger
2004-03-04 20:43 ` Per Andreas Buer
2004-03-03 6:30 ` Hans Reiser
2004-03-03 23:41 ` Johannes Stezenbach
2004-03-05 18:46 ` Pavel Machek
2004-03-06 0:16 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 17:11 Ray Lee
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=40459159.1090501@namesys.com \
--to=reiser@namesys.com \
--cc=ak@suse.de \
--cc=david@southpole.se \
--cc=dax@gurulabs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=ext3-users@redhat.com \
--cc=hch@infradead.org \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=pnelson@andrew.cmu.edu \
--cc=reiserfs-list@namesys.com \
/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