public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	perfctr-devel <perfctr-devel@lists.sourceforge.net>,
	linux-ia64 <linux-ia64@vger.kernel.org>,
	perfmon <perfmon@napali.hpl.hp.com>,
	oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: Re: 2.6.17.1 new perfmon code base, libpfm, pfmon available
Date: Tue, 27 Jun 2006 16:51:25 +0000	[thread overview]
Message-ID: <20060627165125.GA19132@esmail.cup.hp.com> (raw)
In-Reply-To: <20060627143204.GC16417@frankl.hpl.hp.com>

On Tue, Jun 27, 2006 at 07:32:04AM -0700, Stephane Eranian wrote:
...
> > 5006 hardware interrupts in 10 seconds, 16359 interrupt-disable events =>
> > the kernel disabled interrupts 11353 times for critical sections.  To get
> > useful results it looks like booting with idle=poll and disabling cpufreq
> > is needed, though, since interrupts_masked_cycles (non-edge mode) counts
> > even when the CPU is halted:
> 
> Yes, I think you need to be careful with the idle thread, some events may or
> may not count when going low-power. I think it is best to avoid going
> low-power for measurements.

Any benchmarking that involves IA64 idle thread is strongly reccomended
to use "nohalt" option. It's about a 15-20% performance difference
on some interrupt intensive benchmarks (e.g. netperf TCP_RR).

If someone has measured the delta for other architectures that
go into a "low power" state in idle thread, I'd be grateful if
they posted the results or mailed them to me.

thanks,
grant

      reply	other threads:[~2006-06-27 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 14:24 2.6.17.1 new perfmon code base, libpfm, pfmon available Stephane Eranian
2006-06-23 21:13 ` [perfmon] " William Cohen
2006-06-23 21:23   ` [Perfctr-devel] " Stephane Eranian
2006-06-26 17:10     ` [Perfctr-devel] [perfmon] 2.6.17.1 new perfmon code base, libpfm, William Cohen
2006-06-26 17:33 ` 2.6.17.1 new perfmon code base, libpfm, pfmon available Chuck Ebbert
2006-06-26 19:32   ` Grant Grundler
2006-06-26 22:37   ` Stephane Eranian
2006-06-27  5:57 ` Chuck Ebbert
2006-06-27 14:32   ` Stephane Eranian
2006-06-27 16:51     ` Grant Grundler [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=20060627165125.GA19132@esmail.cup.hp.com \
    --to=iod00d@hp.com \
    --cc=76306.1226@compuserve.com \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=perfctr-devel@lists.sourceforge.net \
    --cc=perfmon@napali.hpl.hp.com \
    /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