Date: Wed, 22 Oct 2014 12:20:26 -0400
From: Don Zickus <dzickus@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: eranian@google.com, Peter Zijlstra <peterz@infradead.org>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        Andi Kleen <andi@firstfloor.org>, jolsa@redhat.com, jmario@redhat.com,
        rfowles@redhat.com
Subject: perf:  Translating mmap2 ids into socket info?
Message-ID: <20141022162026.GG135937@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org

Hi,

A question/request came up during our cache to cache analysis.  We were
wondering if give an unique mmap2 id (major, minor, inode, inode
generation), if it was possible to determine a cpu socket id that memory
was attached to at the time of the captured perf event?

We ran into a scenario awhile back where a dcache struct was allocated on
say node2 and then subsequently free'd.  The memory was thought to be
re-allocated on node0 for another dcache entry.  It turned out the memory
was still attached to node2 and was causing slowdowns.

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.


I wasn't involved too much in this problem so the details provided above
are a little hazy.

Anyway, an idea popped up that having socket information might have helped
us solve/notice this problem sooner.

Thoughts?  Not sure if that data is possible.

Cheers,
Don


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/