public inbox for linux-ia64@vger.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] Single bundle loops on Itanium-2 sometimes run slow
Date: Fri, 14 Mar 2003 19:46:50 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806113@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806106@msgid-missing>

>>>>> On Fri, 14 Mar 2003 12:51:43 -0600 (CST), Jack Steiner <steiner@sgi.com> said:

  Jack> SUMMARY: It appears that if a single bundle misaligned loop is
  Jack> interrupted (timer, etc), when the loop is resumed, it
  Jack> sometimes runs at about 1/3 the normal rate until the loop
  Jack> completes. (I dont mean 1 or a few iterations of the loop!!)

  Jack> 	4000000000000eb0: [MIB] adds r8=1,r32
  Jack> 4000000000000eb6: adds r32=-1,r32 4000000000000ebc:
  Jack> br.cloop.sptk.few 4000000000000eb0 <compute+0x60>;;


  Jack> If "noise" is present, pfmon shows significant lost cycles due
  Jack> to BE_LOST_BW_DUE_TO_FE_BR_ILOCK.  A 15 second sample shows:
  Jack> BE_LOST_BW_DUE_TO_FE_BR_ILOCK = 423 for good run
  Jack> BE_LOST_BW_DUE_TO_FE_BR_ILOCK = 105935651 for noisy run

  Jack> Changing the test so that code is at different addresses
  Jack> effects the likelyhood that noise will occur. Sometimes noise
  Jack> occurs on only a subset of the cpus. Sometimes booting a
  Jack> different kernel changes the likelyhood of seeing noise.

  Jack> Has anyone seen this behavior or have an explanation.

Can you check whether the problem goes away when you turn the loop
into a 2-cycle loop?  My bet is that it will.

	--david


  reply	other threads:[~2003-03-14 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 18:51 [Linux-ia64] Single bundle loops on Itanium-2 sometimes run slow Jack Steiner
2003-03-14 19:46 ` David Mosberger [this message]
2003-03-14 20:26 ` Mallick, Asit K

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-105590709806113@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox