From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hardware for venti/fossil/cpu server
Date: Wed, 22 Sep 2004 16:18:59 -0700 [thread overview]
Message-ID: <aa958404acd47e63c3ff0ba2339d0142@collyer.net> (raw)
In-Reply-To: <30255.192.11.222.118.1095913559.squirrel@www.infernopark.com>
Plan 9's kernel would need some work to ensure that it would
run using 64-bit addresses (64-bit integers are supported),
and 8[cal] would need to generate the 64-bit instruction
prefixes. My impression is that it's less work than
a port to a brand-new 64-bit processor but not completely
trivial, as the kernel would need at least an inspection
for places where pointers are assumed to be 32 bits wide.
next prev parent reply other threads:[~2004-09-22 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 8:22 Matthias Teege
2004-09-22 9:24 ` geoff
2004-09-22 10:07 ` Nigel Roles
2004-09-22 10:18 ` geoff
2004-09-22 10:42 ` Nigel Roles
2004-09-22 15:01 ` jmk
2004-09-23 4:25 ` vdharani
2004-09-22 23:18 ` geoff [this message]
2004-09-22 15:19 jmk
2004-09-22 16:21 ` Matthias Teege
2004-09-22 22:57 ` geoff
2004-09-24 0:40 ` Kenji Okamoto
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=aa958404acd47e63c3ff0ba2339d0142@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).