From: David Edelsohn <dje@watson.ibm.com>
To: Cort Dougan <cort@fsmlabs.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, 08 Feb 2001 18:17:31 -0500 [thread overview]
Message-ID: <200102082317.SAA27866@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Cort Dougan <cort@fsmlabs.com> of "Thu, 08 Feb 2001 15:26:42 MST." <20010208152641.P24312@hq.fsmlabs.com>
I do not know which version of AIX you were testing and exactly
how your benchmarks were stressing the system. AIX continually is
improving, just as is the Linux kernel. As I said, the your design was
very good for the particular class of PowerPC implementation that you were
targetting. AIX normally is tuned for a different class of processors and
system configurations than Linux has targeted, so I would not expect them
to have the same sweet spot when running benchmarks.
We currently are in the process of writing some papers about the
system which should explain some of the design decisions. We very much
want to help improve the PowerPC Linux kernel VMM design and interact with
you and other developers. After the current papers are done, we will have
more time to engage in discussions about this.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-08 23:17 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
2001-02-08 22:08 ` David Edelsohn
2001-02-08 22:26 ` Cort Dougan
2001-02-08 23:17 ` David Edelsohn [this message]
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=200102082317.SAA27866@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=cort@fsmlabs.com \
--cc=dan@mvista.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).