[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1805080747480.1849@nuc-kabylake>
Date: Tue, 8 May 2018 07:53:21 -0500 (CDT)
From: Christopher Lameter <cl@...ux.com>
To: "prakash.sangappa" <prakash.sangappa@...cle.com>
cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-api@...r.kernel.org, akpm@...ux-foundation.org,
mhocko@...e.com, kirill.shutemov@...ux.intel.com,
n-horiguchi@...jp.nec.com, drepper@...il.com, rientjes@...gle.com
Subject: Re: [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node
information
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.
Powered by blists - more mailing lists