From: Jesse Pollard <jesse@cats-chateau.net>
To: Jonathan Morton <chromi@cyberspace.org>,
Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>,
dalecki@evision-ventures.com,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 64-bit block sizes on 32-bit systems
Date: Mon, 26 Mar 2001 22:14:17 -0600 [thread overview]
Message-ID: <01032622151501.08410@tabby> (raw)
In-Reply-To: <l0313032eb6e56cd8d6bb@[192.168.239.101]>
In-Reply-To: <l0313032eb6e56cd8d6bb@[192.168.239.101]>
On Mon, 26 Mar 2001, Jonathan Morton wrote:
>>These are NOT the only 64 bit systems - Intel, PPC, IBM (in various guises).
>>If you need raw compute power, the Alpha is pretty good (we have over a
>>1000 in a Cray T3..).
>
>Best of all, the PowerPC and the POWER are binary-compatible to a very
>large degree - just the latter has an extra set of 64-bit instructions.
>What was that I was hearing about having to redevelop or recompile your
>apps for 64-bit?
>
>I can easily imagine a 64-bit filesystem being accessed by a bunch of
>RS/6000s and monitored using an old PowerMac. Goodness, the PowerMac 9600
>even has 6 PCI slots to put all those SCSI-RAID and Ethernet cards in. :)
Save the money - get one fiber channel and connect to all that through
one interface...
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: jesse@cats-chateau.net
Any opinions expressed are solely my own.
next prev parent reply other threads:[~2001-03-27 4:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 21:27 64-bit block sizes on 32-bit systems Jesse Pollard
2001-03-26 22:07 ` Jonathan Morton
2001-03-27 4:14 ` Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2001-03-27 19:57 Jesse Pollard
2001-03-27 20:20 ` Jan Harkes
2001-03-27 21:55 ` LA Walsh
2001-03-27 19:30 Jesse Pollard
[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 17:22 LA Walsh
2001-03-26 19:26 Jesse Pollard
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 17:35 LA Walsh
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
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
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=01032622151501.08410@tabby \
--to=jesse@cats-chateau.net \
--cc=chromi@cyberspace.org \
--cc=dalecki@evision-ventures.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.