linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: eranian@gmail.com, Andi Kleen <andi@firstfloor.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: perf_event: rdpmc self-monitoring overhead issue
Date: Mon, 2 Sep 2013 19:26:59 +0200	[thread overview]
Message-ID: <20130902172659.GJ19750@two.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1309020914030.26568@vincent-weaver-1.um.maine.edu>

> I assume he means MAP_POPULATE

Yes.

> 
> which does improve things, from ~3000 cycles to ~219 cycles but that's 
> still more overhead than the ~130 or so you get by manually touching the 
> page first.

That seems odd. It should be the same.

Can you do a trace-cmd function trace and compare the two cases?

trace-cmd record -p function_graph ...
trace-cmd report

(as usual for tracing perf remove the useless -pg removal for perf in
kernel/events/Makefile and arch/x86/kernel/cpu/Makefile first)

-Andi

      reply	other threads:[~2013-09-02 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 17:55 perf_event: rdpmc self-monitoring overhead issue Vince Weaver
2013-08-30 18:05 ` Stephane Eranian
2013-08-30 18:35   ` Vince Weaver
2013-08-31 10:06     ` Mikael Pettersson
2013-09-02  2:50   ` Andi Kleen
2013-09-02  8:24     ` Stephane Eranian
2013-09-02  9:23       ` Andi Kleen
2013-09-02 13:15       ` Vince Weaver
2013-09-02 17:26         ` Andi Kleen [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=20130902172659.GJ19750@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@redhat.com \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=vincent.weaver@maine.edu \
    /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).