All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] VHPT performance
Date: Fri, 08 Mar 2002 17:31:49 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905241@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905139@msgid-missing>

>>>>> On Fri, 08 Mar 2002 11:26:33 +0100, Christian Hildner <christian.hildner@hob.de> said:

  Christian> Ok that's true. I changed my program so that before the
  Christian> measuring loop there comes the same loop for filling the
  Christian> cache. Also I had to increase the memory size to a
  Christian> minimum of 128 pages because for itanium there are 32
  Christian> entries for L1-DTLB and 96 entries for L2-DTLB. Now I get
  Christian> values of 42 cycles with VHPT enabled and 180 cycles with
  Christian> VHPT disabled. This values are coming near to the ones
  Christian> you found.

Great!

Two other things you may want to try:

 o Use a stride of PAGE_SIZE+LINE_SIZE.  This reduces the likelihood
   of exceeding the cache associativity.

 o Rather than calling printf() in each iteration, collect the results
   in an array and print them once the test is done.  printf() is a monster
   and will blow away a good portion of the first level caches as well as
   a couple of TLB entries.

	--david


      parent reply	other threads:[~2002-03-08 17:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 12:21 [Linux-ia64] VHPT performance Christian Hildner
2002-02-20 17:02 ` Michael Madore
2002-02-20 17:34 ` David Mosberger
2002-02-22 11:35 ` Christian Hildner
2002-02-22 16:58 ` David Mosberger
2002-02-28  8:06 ` Christian Hildner
2002-03-01  2:32 ` David Mosberger
2002-03-08  7:50 ` Christian Hildner
2002-03-08  8:12 ` David Mosberger
2002-03-08 10:26 ` Christian Hildner
2002-03-08 17:31 ` David Mosberger [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=marc-linux-ia64-105590701905241@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.