linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 405 TLB miss reduction
Date: Wed, 10 Dec 2003 12:08:34 -0500	[thread overview]
Message-ID: <3FD75312.7070701@embeddededge.com> (raw)
In-Reply-To: 3FBD5348000912F8@mssbzhh-int.msg.bluewin.ch


Wolfgang Grandegger wrote:

> ....We
> can regain a few percent by using the kernel option CONFIG_PIN_TLB
> but we are thinking about further kernel modifications to reduce
> TLB misses. What comes into my mind is:

If you have a large application I doubt any kernel modification
will gain much.  It's the application causing the huge amounts
of tlb misses, you probably need to evaluate changes that will
reduce that.

It's always easy to pick on the kernel and make some changes
becaue it is a very static and well behaved application.  It
seems your biggest performance increase would come from the
analysis of the application and some redesign to improve its
use of system resources.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-12-10 17:08 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 [this message]
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

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=3FD75312.7070701@embeddededge.com \
    --to=dan@embeddededge.com \
    --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).