From: Cort Dougan <cort@fsmlabs.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: paulus@linuxcare.com.au, Dan Malek <dan@mvista.com>,
Gabriel Paubert <paubert@iram.es>,
tom_gall@vnet.ibm.com, linuxppc-commit@hq.fsmlabs.com,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: context overflow
Date: Thu, 8 Feb 2001 14:28:55 -0700 [thread overview]
Message-ID: <20010208142855.J24312@hq.fsmlabs.com> (raw)
In-Reply-To: <200102081900.OAA25574@mal-ach.watson.ibm.com>; from David Edelsohn on Thu, Feb 08, 2001 at 02:00:07PM -0500
} that the port is not using the PowerPC architecture as intended. By not
} utilizing the hardware assists, the port is not performing at its optimal
} level.
I have data, and have written a paper with Victor and Paul, showing that we
get performance _increases_ by not using the PowerPC MMU architecture as
intended. I think the PPC architecture intentions for the hash table and
TLB and very very poor and restrictive. The 603 was a good step forward
but the 750, 7400 and follow-ons have been steps backwards from this good
start.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-08 21:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 2:27 context overflow Dan Malek
2001-01-22 4:28 ` Troy Benjegerdes
2001-01-22 4:39 ` Tom Gall
2001-01-22 18:10 ` Dan Malek
2001-01-22 18:55 ` tom_gall
2001-01-22 19:59 ` Dan Malek
2001-01-22 22:08 ` tom_gall
2001-01-23 0:10 ` Dan Malek
2001-01-23 10:00 ` Gabriel Paubert
2001-01-23 18:21 ` Dan Malek
2001-02-06 10:55 ` Paul Mackerras
2001-02-06 21:11 ` Dan Malek
2001-02-06 21:50 ` Paul Mackerras
2001-02-06 22:29 ` Dan Malek
2001-02-06 22:45 ` Paul Mackerras
2001-02-06 10:50 ` Paul Mackerras
2001-02-06 21:32 ` Dan Malek
2001-02-06 22:08 ` Paul Mackerras
2001-02-06 23:14 ` Dan Malek
2001-02-07 0:23 ` Paul Mackerras
2001-02-07 18:02 ` Dan Malek
2001-02-08 0:48 ` Paul Mackerras
2001-02-08 1:39 ` Frank Rowand
2001-02-08 19:00 ` David Edelsohn
2001-02-08 20:53 ` Roman Zippel
2001-02-08 21:14 ` David Edelsohn
2001-02-08 23:23 ` Roman Zippel
2001-02-08 23:48 ` Cort Dougan
2001-02-08 21:28 ` Cort Dougan [this message]
2001-02-08 22:08 ` David Edelsohn
2001-02-08 22:26 ` Cort Dougan
2001-02-08 23:17 ` David Edelsohn
2001-02-08 23:27 ` Cort Dougan
2001-02-08 23:28 ` Gabriel Paubert
2001-02-09 9:58 ` Paul Mackerras
2001-02-09 10:57 ` Gabriel Paubert
2001-02-09 11:26 ` Paul Mackerras
2001-02-09 10:49 ` Paul Mackerras
2001-02-07 9:18 ` Roman Zippel
2001-02-07 17:46 ` Dan Malek
2001-02-07 18:39 ` Roman Zippel
2001-02-07 21:16 ` Gabriel Paubert
2001-02-08 0:34 ` Paul Mackerras
2001-01-22 4:55 ` Larry McVoy
2001-01-22 6:15 ` Troy Benjegerdes
2001-01-23 1:12 ` Frank Rowand
2001-01-23 1:20 ` Dan Malek
2001-01-23 2:12 ` Frank Rowand
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=20010208142855.J24312@hq.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=dan@mvista.com \
--cc=dje@watson.ibm.com \
--cc=linuxppc-commit@hq.fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=paulus@linuxcare.com.au \
--cc=tom_gall@vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).