linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: XFS for 2.4
Date: 3 Dec 2003 19:01:39 GMT	[thread overview]
Message-ID: <bqlbuj$j03$1@gatekeeper.tmr.com> (raw)
In-Reply-To: Pine.LNX.4.44.0312020919410.13692-100000@logos.cnet

In article <Pine.LNX.4.44.0312020919410.13692-100000@logos.cnet>,
Marcelo Tosatti  <marcelo.tosatti@cyclades.com> wrote:

| A development tree is much different from a stable tree. You cant just
| simply backport generic VFS changes just because everybody agreed with
| them on the development tree.
| 
| My whole point is "2.6 is almost out of the door and its so much better".  
| Its much faster, much cleaner. 

Yes, a development tree is much different than a stable tree, and even
though the number has gone to 2.6, it's very much a development tree, in
that it's still being used by the same people, and probably not getting
a lot of new testing. Stability is unlikely to be production quality
until fixes go in for problems in mass testing, which won't happen until
it shows up in a vendor release, which won't happen until the vendors
test and clean up what they find... In other words, I don't expect it to
be "really stable" for six months at least, maybe a year.

As for "much faster," let's say that I don't see that on any apples to
apples benchmark. If you measure new threading against 2.4 threading
there is a significant gain, but for anything else the gains just don't
seem to warrant a "much" and there are some regressions shown in other
people's data.

I think 2.6 has new features, it is more scalable, but other than
threads I don't see any huge performance gains.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  parent reply	other threads:[~2003-12-03 19:12 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
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 [this message]
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='bqlbuj$j03$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).