From: Steve Lord <lord@sgi.com>
To: hch@sgi.com, Steve Lord <lord@sgi.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Gonyou, Austin" <austin@coremetrics.com>,
narancs@narancs.tii.matav.hu, linux-xfs@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: XFS to main kernel source
Date: Thu, 20 Sep 2001 16:31:37 -0500 [thread overview]
Message-ID: <200109202131.f8KLVbB19795@jen.americas.sgi.com> (raw)
In-Reply-To: Message from Christoph Hellwig <hch@ns.caldera.de> of "Thu, 20 Sep 2001 22:26:43 +0200." <20010920222643.A7267@caldera.de>
> On Thu, Sep 20, 2001 at 03:16:52PM -0500, Steve Lord wrote:
> > Since we have your attention - which chunks? One of the frustrations we hav
> e
> > had is the lack of feedback from anyone who has looked at XFS.
>
> o The whole vnode layer
Two answers here - economics and code stability. This is a filesystem
which has been worked on by people being payed to do so by a corporation,
therefore there is a budget (long since blown). It was simpler and hence
cheaper to wrap XFS in a conversion layer than to rework the code down
into the bowels of the filesystem. Then the stability part of it, we
started with a working filesystem, from an engineering standpoint it
made more sense to keep as much of the existing code base intact as
possible - the less surgery performed the better in terms of keeping
things running, and making it easy to take enhancements and fixes made
in the Irix base into the Linux code (we don't do it the other way around).
> o checks already peformed by the VFS all over the place
> (just take a look at xfs_rename.c!)
I think I will answer this one more slowly and in response to Al Viro's
email. But that economics/stability thing comes into it again.
> o the own quoata code
XFS quotas are transactional, when space is added to a file the quota is
adjusted in the same transaction. It is fairly hard to do this without your
own quota code.
> o the hooks for a propritary clusterfs..
Well we have to make money on something you know.... and in reality
there are not a lot of them in the filesystem.
Thanks
Steve
>
> My 2 (euro-)cents,
>
> Christoph
>
> --
> Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-09-20 21:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 20:07 Gonyou, Austin
2001-09-20 20:14 ` Alan Cox
2001-09-20 20:16 ` Steve Lord
2001-09-20 20:25 ` Alan Cox
2001-09-20 20:26 ` Christoph Hellwig
2001-09-20 21:31 ` Steve Lord [this message]
2001-09-21 3:12 ` Andreas Dilger
2001-09-21 3:25 ` Steve Lord
2001-09-21 4:42 ` Nathan Scott
2001-09-21 5:58 ` Christoph Hellwig
2001-09-21 8:40 ` Narancs v1
2001-09-21 14:19 ` Alexander Viro
2001-09-21 14:45 ` Steve Lord
2001-09-20 20:40 ` Alexander Viro
2001-09-21 18:03 ` Steve Lord
2001-09-20 20:29 ` Horst von Brand
2001-09-20 20:50 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 23:32 [PATCH] Remove needless BKL from release functions David C. Hansen
2001-11-22 10:12 ` Oliver Neukum
2001-11-22 12:11 ` Christoph Hellwig
2001-11-22 12:30 ` Horst von Brand
2001-11-22 13:05 ` Christoph Hellwig
2001-11-23 9:44 ` Rick Lindsley
2001-11-23 10:10 ` Oliver.Neukum
2001-11-23 10:47 ` Christoph Hellwig
2001-11-23 11:24 ` Oliver Neukum
2001-11-26 17:46 ` David C. Hansen
2001-11-26 19:41 ` Flavio Stanchina
2001-11-26 19:53 ` David C. Hansen
2001-11-23 12:08 ` Rick Lindsley
2001-11-06 20:04 [PATCH] lp.c, eexpress.c jiffies cleanup Tim Schmielau
2001-11-06 21:15 ` Andreas Dilger
2001-11-06 21:37 ` Philip Blundell
2001-11-07 0:10 ` Andreas Dilger
2001-11-06 23:58 ` Tim Hockin
2001-09-20 18:12 XFS to main kernel source Narancs v1
2001-09-20 20:02 ` Alan Cox
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=200109202131.f8KLVbB19795@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=austin@coremetrics.com \
--cc=hch@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=narancs@narancs.tii.matav.hu \
/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
all inboxes | Powered by JetHome®