All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: compiling libc5 on UP1.0
Date: Sun, 10 May 1998 04:10:11 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222356530999@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222356530996@msgid-missing>

   From: Eiki Ito <eiki@hal.com>
   Date: 	Sat, 9 May 1998 20:57:06 -0700 (PDT)

   SPARC64-III's memory management is quite different from SPARC64-I
   and II, much closer to Ultrasparc.  TLB format is (I think) the
   only major difference.  No advertise, but if you are interested
   please refer to Microprocessor Report 12/08/97.

Oh great, finally they are using a software replace TLB miss design in
Hal's sparc64.  You'll benefit greatly from the work I am doing
tonight using virtual page tables, TLB misses cost 8 instructions and
only one memory reference now.

Later,
David S. Miller
davem@dm.cobaltmicro.com

      parent reply	other threads:[~1998-05-10  4:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-10  2:20 compiling libc5 on UP1.0 Eiki Ito
1998-05-10  2:27 ` David S. Miller
1998-05-10  3:57 ` Eiki Ito
1998-05-10  4:10 ` David S. Miller [this message]

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-90222356530999@msgid-missing \
    --to=davem@dm.cobaltmicro.com \
    --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.