From: David Gibson <david@gibson.dropbear.id.au>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: LMbench results for large page patch
Date: Thu, 6 Jun 2002 17:57:32 +1000 [thread overview]
Message-ID: <20020606075732.GY2630@zax> (raw)
In-Reply-To: <3CFF0F88.5020600@embeddededge.com>
On Thu, Jun 06, 2002 at 03:30:16AM -0400, Dan Malek wrote:
>
> David Gibson wrote:
>
> > ....There are a couple of things largepte still does better
> >on, main memory latency (expected) and exec proc (unexpected). The
> >difference is small though.
>
> The exec proc does lots of VM updates and TLB management. The pinned
> TLBs on the 4xx require additional management overhead to ensure they
> aren't flushed when it is viewed as quicker to just flush the TLB.
> The exec proc tests don't accomplish any useful work once the system
> resources are allocated, so you are continually turning over the TLB and
> any additional managemant will appear in this overhead.
Ah yes, that makes sense. In particular _tlbia() will be much slower
with pinned TLBs than without.
> > largepte still does as well or better than nopintlb in
> >essentially every case.
>
> Which is expected....now if we could just extend this to applications, we
> would really have something :-)
So are you ok with the notion of merging the large page stuff and
abolishing CONFIG_PIN_TLB, once I've made iopa() and mapin_ram() less
ugly than they are in that first cut?
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-06 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 7:08 LMbench results for large page patch David Gibson
2002-06-06 4:29 ` David Gibson
2002-06-06 7:30 ` Dan Malek
2002-06-06 7:57 ` David Gibson [this message]
2002-06-06 8:14 ` Dan Malek
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=20020606075732.GY2630@zax \
--to=david@gibson.dropbear.id.au \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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).