From: John Richard Moser <nigelenki@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: IA-32 on x86-64
Date: Sat, 20 May 2006 09:03:11 -0400 [thread overview]
Message-ID: <446F138F.4020801@comcast.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Does anyone know how to check if I'm running an IA-32 process on x86-64?
More importantly, how do I tell how big the user VM space is for
current? Like 3GiB for x86 and who knows what (87GiB? 192GiB?) for
x86-64 and however much for sparc/ppc ....
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
Creative brains are a valuable, limited resource. They shouldn't be
wasted on re-inventing the wheel when there are so many fascinating
new problems waiting out there.
-- Eric Steven Raymond
We will enslave their women, eat their children and rape their
cattle!
-- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRG8Tjgs1xW0HCTEFAQLGPw/+MnsPqRchMPTfPAnmElB1I0drQpGKSzXM
fbalToXhv1EKWnPN/Sj8JdVenech3okH75W6/Y+OGMOjTWYw46uvhVr9KBcXWxRU
3+Fkx6iJPTIklhOWkbxZKnDirFttZnAh0oU0akRv8ko8Y25siohRU5WU/ALulq1l
ntlgHRz0mFhrVNukBEklq7nPre5/xJHLuwvDh2DKeMSbPHH5AsMC5li2Aa8tU72E
C83cwrRfGF5rUvlz7ILU/CeWfLU2TyVH/ow/zUzs9Snbndpo9KCekm+MwdUGj3YP
zt+bSMyKafBzpkrKrG11hm8l4j2Sxw9LdOCtD9Vbfu1e6YORnh/KHx6NNQ9+HibH
7UHZjlYwMq8I9VvJEWGcU43IsDp5q0VQ0W2vcEvdVcPmhmB2cRVljOdxXTQCAN86
ET2v6glufIvKy38ThO81zhgoxdnpGvJP4Tec34zihaNGDQ/jkzA23O8/8SLwFHr6
TizaQQsQLCAGOTRhGK4Phl2Yp+VJeKO9mq0vjAb9OBMl05MgLlqcJGm+MdLC1n+m
FxHs568tPp07EnjX1UlADXVUa8dAHbjFPAyupW/M/HIe1uv5fbwB9kn0MAlVqm2u
7AkMfiFhgv6Bvoylb2b17iWDbsLBo0N77++9r1Wn5bRkU99rfCTwmI1fBrH57Q5N
N2qNcoKBXpY=
=Nzyw
-----END PGP SIGNATURE-----
next reply other threads:[~2006-05-20 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 13:03 John Richard Moser [this message]
2006-05-20 21:37 ` IA-32 on x86-64 Jan Engelhardt
2006-05-20 21:41 ` Kyle McMartin
2006-05-20 22:09 ` John Richard Moser
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=446F138F.4020801@comcast.net \
--to=nigelenki@comcast.net \
--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 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.