linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS for 2.4
Date: Tue, 2 Dec 2003 09:10:58 +1100	[thread overview]
Message-ID: <20031201221058.GA621@frodo> (raw)
In-Reply-To: <Pine.LNX.4.44.0312011202330.13692-100000@logos.cnet>

On Mon, Dec 01, 2003 at 12:06:14PM -0200, Marcelo Tosatti wrote:
> On Mon, 1 Dec 2003, Nathan Scott wrote:
> 
> > Hi Marcelo,
> > 
> > Please do a
> > 
> > 	bk pull http://xfs.org:8090/linux-2.4+coreXFS
> > 
> > This will merge the core 2.4 kernel changes required for supporting
> > the XFS filesystem, as listed below.  If this all looks acceptable,
> > then please also pull the filesystem-specific code (fs/xfs/*)
> > 
> > 	bk pull http://xfs.org:8090/linux-2.4+justXFS
> 
> Nathan, 
> 
> I think XFS should be a 2.6 only feature.
> 
> 2.6 is already stable enough for people to use it. 
> 

Hi Marcelo,

Please reconsider -- the "core" kernel changes we need have existed
for three+ years outside of the mainline tree, and each is a small
and easily understood change that doesn't affect other filesystems.
There is also a VFS fix in there from Ethan Benson, as we discussed
during 2.4.23-pre, when you asked us to resend XFS for 2.4.24-pre!)
Everything there is a backport from 2.6 in some form, there should
be no surprises.

Not having XFS in 2.4 is extremely disadvantageous for us XFS folks
(especially since every other journaled filesystem has been merged
now).  To our users it means some rescue disks simply don't support
XFS, meaning you can't mount filesystems when you _really_ need to,
etc, etc.  Its also always extra work for distributors to merge XFS
themselves, and hence a few just don't (and occasionally tell us
that they are waiting for you to merge it) - which means some users
don't even get the option of using XFS, despite our best efforts.

>From discussions with distributors, a stable 2.6 distribution will
be many months after 2.6.0 is officially released, so these issues
are not going to go away anytime soon.

So, please merge XFS this time round - its actively developed, has
a large installed user base, and has been maintained outside of 2.4
for a long time.  We have waited patiently as each release goes by
for you to give us the nod, and have been knocked back on a number
of occasions while various other merges are being done.

cheers.

-- 
Nathan

  reply	other threads:[~2003-12-01 22:11 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  6:20 XFS for 2.4 Nathan Scott
2003-12-01  9:24 ` Jens Axboe
2003-12-01  9:44   ` Stefan Smietanowski
2003-12-01  9:45     ` Jens Axboe
2003-12-01 14:06 ` Marcelo Tosatti
2003-12-01 22:10   ` Nathan Scott [this message]
2003-12-01 22:20     ` Larry McVoy
2003-12-02  0:23       ` Nathan Scott
2003-12-02 11:22         ` Marcelo Tosatti
2003-12-02 18:05           ` Austin Gonyou
2003-12-02 19:55           ` Stephan von Krawczynski
2003-12-02 20:05             ` Marcelo Tosatti
2003-12-02 20:16             ` Lawrence Walton
2003-12-03 19:01           ` bill davidsen
2003-12-03 20:45             ` Willy Tarreau
2003-12-03 21:17               ` bill davidsen
2003-12-03 21:48                 ` Joel Becker
2003-12-03 22:17                   ` bill davidsen
2003-12-03 22:08                 ` Ed Sweetman
2003-12-04  5:21                   ` Willy Tarreau
2003-12-04  0:34               ` Clemens Schwaighofer
2003-12-04  5:33                 ` Willy Tarreau
2003-12-04 10:13                   ` Clemens Schwaighofer
2003-12-02 11:18     ` Marcelo Tosatti
2003-12-02 11:48       ` Marcelo Tosatti
2003-12-02 15:34       ` Russell Cattelan
2003-12-02 15:50         ` Marcelo Tosatti
2003-12-02 16:10           ` Darrell Michaud
2003-12-02 16:21             ` Austin Gonyou
2003-12-02 16:28             ` Jeff Garzik
2003-12-02 16:57               ` venom
2003-12-02 17:41               ` Stefan Smietanowski
2003-12-02 18:01           ` Russell Cattelan
2003-12-02 16:13         ` Jeremy Jackson
2003-12-02  0:51   ` Clemens Schwaighofer
2003-12-02  1:26     ` Marcos D. Marado Torres
2003-12-14  1:08   ` 2.4 vs 2.6 Jan Rychter
2003-12-14  1:01     ` Roberto Sanchez
2003-12-14 11:23       ` Måns Rullgård
2003-12-14 18:09         ` Daniel Gryniewicz
2003-12-14  1:53     ` Daniel Gryniewicz
2003-12-14  2:01     ` coderman
2003-12-14 20:23       ` tabris
2003-12-14  7:05     ` Voicu Liviu
2003-12-14 16:01       ` Roberto Sanchez
2003-12-14 17:32         ` Voicu Liviu
2003-12-15  7:23           ` Harry McGregor
2003-12-15  7:51             ` Voicu Liviu
2003-12-14 11:24     ` Frederik Deweerdt
2003-12-01 21:00 ` XFS for 2.4 Dan Yocum
2003-12-01 21:50   ` Bryan Whitehead
2003-12-01 22:01     ` Jeffrey E. Hundstad
2003-12-01 22:13     ` Gerardo Exequiel Pozzi
2003-12-02  2:54     ` Joshua Schmidlkofer
2003-12-02 11:02   ` Maciej Soltysiak
2003-12-02 17:45 Murthy Kambhampaty
2003-12-02 17:59 ` Jeff Garzik
2003-12-03 20:10   ` bill davidsen
2003-12-02 18:01 ` Marcelo Tosatti
2003-12-02 19:10   ` Tomas Szepe
2003-12-03  0:13     ` Eric Sandall
2003-12-03 20:12       ` bill davidsen
2003-12-02 18:02 ` Larry McVoy
2003-12-02 18:11   ` Christoph Hellwig
     [not found]     ` <20031202181146.A27567@adic.com>
2003-12-02 18:19       ` Steve Lord
2003-12-02 18:20     ` Larry McVoy
2003-12-02 18:23       ` Christoph Hellwig
2003-12-02 18:27         ` Christoph Hellwig
2003-12-02 19:12           ` Marcelo Tosatti
2003-12-02 20:10             ` Nathan Scott
2003-12-02 20:11         ` viro
2003-12-03 20:51       ` bill davidsen
2003-12-03 20:44   ` bill davidsen
2003-12-03 21:06     ` Marcelo Tosatti
2003-12-03 22:07     ` grundig
2003-12-03 22:48       ` bill davidsen
2003-12-02 18:34 Murthy Kambhampaty
2003-12-04  1:27 Xose Vazquez Perez
2003-12-04  2:40 ` Bernd Eckenfels

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=20031201221058.GA621@frodo \
    --to=nathans@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=marcelo.tosatti@cyclades.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;
as well as URLs for NNTP newsgroup(s).