From: <pau@readysoft.es>
To: ultralinux@vger.kernel.org
Subject: Re: Post 1.2 development
Date: Mon, 29 Mar 1999 09:17:31 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-92270303505528@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92258097010860@msgid-missing>
On Sat, 27 Mar 1999, David Miller wrote:
> 1. What can we expect in the way of a time frame for a peek at
> 64-bit userland? Are we talking about 1-2 months, 6 months or a
> year? This is a really critical piece of information for ISVs
> contemplating porting to UltraPenguin.
>
> I believe I told you in private email a few weeks ago that we are
> currently shooting for some time near mid-summer. But as usual, no
> promises.
>
> That being said, I believe people who are porting applications which
> have no real need for 64-bits are making a mistake by making a 64-bit
> sparc version of their application. This is simply because if they
> make a 32-bit version then the whole sparc line of systems can run
> that application.
>
> The 64-bit userland will be slightly slower for most applications, and
> this is just a fact of life not anything to do with how our
> implementation will work (pointers and types are bigger, thus the
> memory references of the application, even for common tasks, will be
> larger).
Then, will we be able to support more than 2^16 users per machine,
i.e. 2^32?
Pau
next prev parent reply other threads:[~1999-03-29 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-28 0:22 Post 1.2 development David Van Beveren
1999-03-28 0:53 ` David Miller
1999-03-29 9:17 ` pau [this message]
1999-03-29 9:29 ` pau
1999-03-29 10:22 ` Jakub Jelinek
1999-03-29 10:37 ` David Miller
1999-03-29 20:35 ` Scott Michel
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=marc-linux-ultrasparc-92270303505528@msgid-missing \
--to=pau@readysoft.es \
--cc=ultralinux@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.