All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Felix von Leitner <usenet-20020126@fefe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about sparc 64-bit user land
Date: Sat, 26 Jan 2002 12:25:05 -0500	[thread overview]
Message-ID: <3C52E671.605FA2F3@mandrakesoft.com> (raw)
In-Reply-To: <20020126171545.GB11344@fefe.de>

Felix von Leitner wrote:
> 
> My understanding is that there is no 64-bit user land support for
> UltraSPARC, although the kernel runs in 64-bit mode.  Is that correct?
> If yes: why is that (still) so?

sparc64 has an in-kernel thunk layer that lets it run sparc32 binaries,
and a sparc32 userland.

Presumeably the standard benefits apply for 32 over 64 bits, such as
lower I-cache usage and smaller programs overall.  Though most
Linux/Unix applications seem to work ok on 64-bit, (a) some don't and
(b) few apps actually take good advantage of 64-bit machine int and
address space.

Of course, all that said, coming from an Alpha AXP background I prefer
64-bit userland ;-)

	Jeff


-- 
Jeff Garzik      | "I went through my candy like hot oatmeal
Building 1024    |  through an internally-buttered weasel."
MandrakeSoft     |             - goats.com

  parent reply	other threads:[~2002-01-26 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-26 17:15 question about sparc 64-bit user land Felix von Leitner
2002-01-26 17:24 ` Ben Collins
2002-01-26 17:25 ` Jeff Garzik [this message]
2002-01-27 14:11   ` CRAP in 2.4.18-pre7 Martin Dalecki
2002-01-27 16:50     ` Jeff Garzik
2002-01-27 17:32       ` Martin Dalecki
2002-01-27 17:53         ` root
2002-01-27 21:08           ` H. Peter Anvin
2002-01-28 12:06             ` Martin Dalecki
2002-01-28 15:37               ` H. Peter Anvin
2002-01-27 18:46     ` Michal Jaegermann
2002-01-27 21:58       ` Stephan von Krawczynski
2002-01-28  3:40         ` Michal Jaegermann
2002-01-26 18:07 ` question about sparc 64-bit user land Andreas Jaeger

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=3C52E671.605FA2F3@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=usenet-20020126@fefe.de \
    /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.