On 05/07/2018 07:47 AM, Christopher Lameter wrote:
On Fri, 4 May 2018, Prakash Sangappa wrote:
Currently 'numa_maps' gives a list of numa nodes, memory is allocated per
VMA.
Ex. we get something like from numa_maps.
04000 N0=1,N2=2 kernelpagesize_KB=4
First is the start address of a VMA. This VMA could be much larger then 3 4k
pages.
It does not say which address in the VMA has the pages mapped.
Not precise. First the address is there as you already said. That is the
virtual address of the beginning of the VMA. What is missing? You need
Yes,
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.
