public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: Steve Lord <lord@sgi.com>
Cc: 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: Fri, 21 Sep 2001 07:58:54 +0200	[thread overview]
Message-ID: <20010921075854.A11617@caldera.de> (raw)
In-Reply-To: <hch@ns.caldera.de> <200109202131.f8KLVbB19795@jen.americas.sgi.com>
In-Reply-To: <200109202131.f8KLVbB19795@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 20, 2001 at 04:31:37PM -0500

On Thu, Sep 20, 2001 at 04:31:37PM -0500, Steve Lord wrote:
> >  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).

I completly understand SGI's reson to do this - but yet I don't want to
see such code in the mainline for obvios reasons..

> >  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.

Again I understand SGI's reasoning - but such hooks are usually not
considered to be a good thing line.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

  parent reply	other threads:[~2001-09-21  6:00 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 20:07 XFS to main kernel source 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
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 [this message]
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
     [not found] <adilger@turbolabs.com>
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=20010921075854.A11617@caldera.de \
    --to=hch@ns.caldera.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=austin@coremetrics.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=lord@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