From: Andreas Dilger <adilger@turbolinux.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Andreas Dilger <adilger@turbolinux.com>, LA Walsh <law@sgi.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: 64-bit block sizes on 32-bit systems
Date: Mon, 26 Mar 2001 12:09:04 -0700 (MST) [thread overview]
Message-ID: <200103261909.f2QJ95O19914@webber.adilger.int> (raw)
In-Reply-To: <20010326190945.I31126@parcelfarce.linux.theplanet.co.uk> from Matthew Wilcox at "Mar 26, 2001 07:09:45 pm"
Matthew Wilcox writes:
> On Mon, Mar 26, 2001 at 10:47:13AM -0700, Andreas Dilger wrote:
> > What do you mean by problems 5 years down the road? The real issue is that
> > this 32-bit block count limit affects composite devices like MD RAID and
> > LVM today, not just individual disks. There have been several postings
> > I have seen with people having a problem _today_ with a 2TB limit on
> > devices.
>
> people who can afford 2TB of disc can afford to buy a 64-bit processor.
Get real. If you buy (cheapest) 40GB IDE disks, I can have 2TB for
U$9200 (not including controllers). In 1 year it will be half, etc.
I expect I will start moving my DVD collection to disk storage in an
ia32 system once price/GB falls by 50% from current levels. This is
just for home use, let alone what large companies want to do. I am
fully expecting hard drive price/GB to keep falling at its current rate.
This whole "64-bit" fallacy has got to stop. First it was "anybody
who needs files > 2GB should use a 64-bit CPU", wrong. Then it was
"anybody who needs > 1GB RAM should use a 64-bit CPU", wrong. Now it is
"anybody who needs > 2TB disk should use a 64-bit CPU", soon to be wrong.
I don't think the millions of 32-bit systems will disappear overnight,
or even in 10 years, yet we already have single IDE disks > 100GB, and
in 2 or 3 years we will have single IDE disks > 1TB that people will
want to use in their 32-bit systems.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-26 19:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 16:39 LA Walsh
2001-03-26 17:18 ` Matthew Wilcox
2001-03-26 17:47 ` Andreas Dilger
2001-03-26 18:09 ` Matthew Wilcox
2001-03-26 18:37 ` Eric W. Biederman
2001-03-26 19:36 ` Martin Dalecki
2001-03-26 23:03 ` AJ Lewis
2001-03-26 19:05 ` Scott Laird
2001-03-26 19:09 ` Andreas Dilger [this message]
2001-03-26 20:31 ` Dan Hollis
2001-03-26 19:20 ` Rik van Riel
2001-03-26 20:14 ` Jes Sorensen
2001-03-26 17:58 ` Eric W. Biederman
2001-03-28 8:06 ` Matthew Wilcox
2001-03-26 17:35 LA Walsh
2001-03-26 18:01 Manfred Spraul
2001-03-26 18:07 ` Matthew Wilcox
2001-03-26 19:40 ` LA Walsh
2001-03-26 21:53 ` Manfred Spraul
2001-03-26 22:07 ` LA Walsh
2001-03-26 19:26 Jesse Pollard
2001-03-26 21:27 Jesse Pollard
2001-03-26 22:07 ` Jonathan Morton
2001-03-27 4:14 ` Jesse Pollard
2001-03-27 17:22 LA Walsh
[not found] <Pine.LNX.4.30.0103270022500.21075-100000@age.cs.columbia.edu>
[not found] ` <3AC0CA9C.3D804361@sgi.com>
2001-03-27 19:00 ` Jan Harkes
2001-03-27 19:30 Jesse Pollard
2001-03-27 19:57 Jesse Pollard
2001-03-27 20:20 ` Jan Harkes
2001-03-27 21:55 ` LA Walsh
2001-03-27 22:23 Jesse Pollard
2001-03-27 23:56 ` Steve Lord
2001-03-28 8:09 ` Brad Boyer
2001-03-28 14:53 ` Dave Kleikamp
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=200103261909.f2QJ95O19914@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=law@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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®