public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <landley@webofficenow.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: linux-kernel@vger.kernel.org (lkml)
Subject: Re: Stability of ReiserFS onj Kernel 2.4.x (sp. 2.4.[56]{-ac*}
Date: Tue, 17 Jul 2001 15:40:15 -0400	[thread overview]
Message-ID: <01071715401507.13440@localhost.localdomain> (raw)
In-Reply-To: <200107160022.f6G0MBn310960@saturn.cs.uml.edu>
In-Reply-To: <200107160022.f6G0MBn310960@saturn.cs.uml.edu>

On Sunday 15 July 2001 20:22, Albert D. Cahalan wrote:

> An extra 4 bits buys us 6 years maybe. Nice, except that we
> already have people complaining. Maybe somebody remembers when
> the complaining started.

I blame Charles Babbage, myself...

As for the scalable block numbers, assuming moore's law holds at 18 
months/doubling without hitting subatomic quantum weirdness limits, the jump 
from 32 to 64 bits gives us another 48 years.  48 years ago was 1953.  Univac 
(powered by vacuum tubes) hit the market in 1951.  Project whirlwind would do 
prototype work applying transistors to computers in 1954.

Just a sense of perspective.  Scalable block numbers sound cool if they save 
metadata space, but not as a source of extra scalability.  And they sound 
like a can of worms in terms of complexity.

Feel free to bring up the Y2K problem as a counter-example as to why 
"rewriting it when it becomes a problem" is a bad idea.  But the problem 
there was closed (and lost) source code, wasn't it?

Rob


  parent reply	other threads:[~2001-07-20  1:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 23:54 Stability of ReiserFS onj Kernel 2.4.x (sp. 2.4.[56]{-ac*} Adam Schrotenboer
2001-07-15  0:01 ` Thomas Zimmerman
2001-07-15 16:00 ` volodya
2001-07-15 16:08   ` Alexander Viro
2001-07-16  0:50     ` volodya
2001-07-16  0:54       ` Ragnar Kjørstad
2001-07-16  0:57       ` Alexander Viro
2001-07-16  1:22         ` volodya
2001-07-16  1:48           ` Ignacio Vazquez-Abrams
2001-07-15 16:33   ` Alan Cox
2001-07-15 16:44     ` Hans Reiser
2001-07-15 16:46       ` Alan Cox
2001-07-15 17:54         ` Hans Reiser
2001-07-15 18:17           ` Alan Cox
2001-07-16 13:27         ` Marco Colombo
2001-07-15 17:58       ` Rob Turk
2001-07-15 21:30       ` Daniel Phillips
2001-07-15 22:05         ` Hans Reiser
2001-07-15 22:18           ` Daniel Phillips
2001-07-16  0:22         ` Albert D. Cahalan
2001-07-16 12:49           ` Daniel Phillips
2001-07-17 19:40           ` Rob Landley [this message]
2001-07-16 17:19         ` Jussi Laako
2001-07-16 17:53           ` Daniel Phillips
2001-07-16 19:16           ` Hans Reiser
2001-07-16 21:00             ` Jussi Laako
2001-07-16 22:28             ` Daniel Phillips
2001-07-18  0:58           ` Dan Hollis
2001-07-16  4:39   ` Mike A. Harris

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=01071715401507.13440@localhost.localdomain \
    --to=landley@webofficenow.com \
    --cc=acahalan@cs.uml.edu \
    --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