From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Don Zickus <dzickus@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
eranian@google.com, Andi Kleen <andi@firstfloor.org>,
jolsa@redhat.com, jmario@redhat.com, rfowles@redhat.com
Subject: Re: perf: Translating mmap2 ids into socket info?
Date: Wed, 22 Oct 2014 14:42:26 -0300 [thread overview]
Message-ID: <20141022174226.GF4160@kernel.org> (raw)
In-Reply-To: <20141022164510.GJ21513@worktop.programming.kicks-ass.net>
Em Wed, Oct 22, 2014 at 06:45:10PM +0200, Peter Zijlstra escreveu:
> On Wed, Oct 22, 2014 at 12:20:26PM -0400, Don Zickus wrote:
> > Our cache-to-cache tool noticed the slowdown but we couldn't understand
> > why because we had falsely assumed the memory was allocated on the local
> > node but instead it was on the remote node.
> But in general, you can never say for user memory, since that has the
> process page table mapping in between, the user virtual address is
> unrelated to backing (and can change frequently and without
> notification).
> Therefore the mmap(2) information is useless for this, it only concerns
> user memory.
So what you are saying is that it is difficult to have some sort of
mechanism that an mmap moved from one node to another, when that
happens, i.e. a new tracepoint for that?
- Arnaldo
next prev parent reply other threads:[~2014-10-22 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 16:20 perf: Translating mmap2 ids into socket info? Don Zickus
2014-10-22 16:45 ` Peter Zijlstra
2014-10-22 17:42 ` Arnaldo Carvalho de Melo [this message]
2014-10-22 18:15 ` Arnaldo Carvalho de Melo
2014-10-22 19:55 ` Peter Zijlstra
2014-10-22 19:54 ` Peter Zijlstra
2014-10-22 18:09 ` Joe Mario
2014-10-22 20:02 ` Peter Zijlstra
2014-10-22 20:38 ` Don Zickus
2014-10-23 11:01 ` Peter Zijlstra
2014-10-23 11:30 ` Peter Zijlstra
2014-10-23 13:10 ` Don Zickus
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=20141022174226.GF4160@kernel.org \
--to=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=jmario@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rfowles@redhat.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