From: Jon Masters <jonathan@jonmasters.org>
To: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405 TLB miss reduction
Date: Thu, 11 Dec 2003 16:44:02 +0000 [thread overview]
Message-ID: <3FD89ED2.6080204@jonmasters.org> (raw)
In-Reply-To: <3FBD5348000912F8@mssbzhh-int.msg.bluewin.ch>
Wolfgang Grandegger wrote:
| Has anybody already investigated the effort or benefit of such
| changes or knows about other (simple) measures (apart from
| replacing the hardware)?
I have been thinking about doing something slightly more intelligent
with tLB miss handling and selecting the next entry to write.
At the moment I am doing stuff like setting up PTXdist (which does
indeed rule by the way once you get the right configuration) however I
could do with something for the holiday period so please keep me updated
~ and I will try to fit bits in when I get time with a board to do it.
There is an EPPC405 which I am hoping to borrow for a while because it
is not particularly being used but I will see what happens about it.
Cheers,
Jon.
P.S. I am going to be at FOSDEM and welcome the idea of meeting other
ppc 405 or Virtex II Pro or indeed anyone from this list.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-11 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 14:43 405 TLB miss reduction Wolfgang Grandegger
2003-12-10 16:03 ` Matt Porter
2003-12-11 9:06 ` Wolfgang Grandegger
2003-12-11 15:46 ` Dan Malek
2003-12-11 17:45 ` Matt Porter
2003-12-12 9:50 ` Wolfgang Grandegger
2003-12-15 11:26 ` Joakim Tjernlund
2003-12-10 17:08 ` Dan Malek
2003-12-11 10:37 ` Wolfgang Grandegger
2003-12-11 16:48 ` Jon Masters
2003-12-11 16:56 ` Wolfgang Grandegger
2003-12-11 17:06 ` Jon Masters
2003-12-11 17:36 ` Matt Porter
2003-12-11 16:44 ` Jon Masters [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=3FD89ED2.6080204@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wolfgang.grandegger@bluewin.ch \
/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).