All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Lehmann <aaronl@vitelus.com>
To: linux-kernel@vger.kernel.org, jakub@redhat.com, davem@redhat.com
Subject: Linux speed on sun4c
Date: Sat, 30 Jun 2001 22:06:12 -0700	[thread overview]
Message-ID: <20010630220612.C14361@vitelus.com> (raw)


NetBSD/Sparc's FAQ asserts:

    Why is NetBSD so much faster than SparcLinux on sun4c (top) 

        The memory management hardware on sun4c machines (SPARCStation
        1, 1+, 2, IPC, IPX, SLC, ELC and clones) is not handled particularly
        well by Linux. Until Linux reworks their MMU code NetBSD will be very
        much faster on this hardware. 

Was there ever any truth to this statement? It seems to be light on
technical details. Have these purported issues ever been fixed?

I don't want to be scared into running NetBSD on my SparcStation 2 :D.

             reply	other threads:[~2001-07-01  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-01  5:06 Aaron Lehmann [this message]
2001-07-01  6:36 ` Linux speed on sun4c David S. Miller
2001-07-03 15:59   ` Guenter Millahn
2001-07-03 23:07     ` David S. Miller
2004-10-21 11:33       ` Nico Schottelius

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=20010630220612.C14361@vitelus.com \
    --to=aaronl@vitelus.com \
    --cc=davem@redhat.com \
    --cc=jakub@redhat.com \
    --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.