home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!dog.ee.lbl.gov!horse.ee.lbl.gov!torek
- From: torek@horse.ee.lbl.gov (Chris Torek)
- Newsgroups: comp.arch
- Subject: 64-bit file sizes (was More Alpha AXP Performance Numbers)
- Date: 19 Nov 1992 18:32:14 GMT
- Organization: Lawrence Berkeley Laboratory, Berkeley
- Lines: 19
- Message-ID: <27540@dog.ee.lbl.gov>
- References: <Bxo927.ECF.2@cs.cmu.edu> <1992Nov17.041026.27756@ntuix.ntu.ac.sg>
- Reply-To: torek@horse.ee.lbl.gov (Chris Torek)
- NNTP-Posting-Host: 128.3.112.15
-
- (N.B.: this has little relevance to comp.arch. Followups should probably
- be directed elsewhere, not that there should really be any followups.)
-
- In article <1992Nov17.041026.27756@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg
- (Othman Ahmad) writes:
- >... With current 32-bit BSD unix, it can only access 2Gbyte addresses.
-
- Current BSD Unix (4.4BSD-alpha) has 64-bit sizes. There are still
- some internal limits from 32-bit `block' numbers, but the external
- interface provides signed 64-bit offsets.
-
- >Must be a 64-bit version of Unix or VMS. Will it cause problems in
- >porting software to apha?
-
- From experience, yes. The breakage is easy to fix once detected, but
- does occur.
- --
- In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427)
- Berkeley, CA Domain: torek@ee.lbl.gov
-