From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Lameter Subject: Re: [RFC PATCH] Add /proc//numa_vamaps for numa node information Date: Tue, 8 May 2018 07:53:21 -0500 (CDT) Message-ID: References: <1525240686-13335-1-git-send-email-prakash.sangappa@oracle.com> <98e34010-d55a-5f2d-7d98-cba424de2e74@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: "prakash.sangappa" Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-api@vger.kernel.org, akpm@linux-foundation.org, mhocko@suse.com, kirill.shutemov@linux.intel.com, n-horiguchi@ah.jp.nec.com, drepper@gmail.com, rientjes@google.com List-Id: linux-api@vger.kernel.org On Mon, 7 May 2018, prakash.sangappa wrote: > > each address for each page? Length of the VMA segment? > > Physical address? > > Need numa node information for each virtual address with pages mapped. > No need of physical address. You need per page information? Note that there can only be one page per virtual address. Or are we talking about address ranges? https://www.kernel.org/doc/Documentation/vm/pagemap.txt ? Also the move_pages syscall has the ability to determine the location of individual pages.