From: Christopher Lameter <cl@linux.com>
To: Prakash Sangappa <prakash.sangappa@oracle.com>
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
Subject: Re: [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node information
Date: Mon, 7 May 2018 09:47:17 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1805070945200.21162@nuc-kabylake> (raw)
In-Reply-To: <98e34010-d55a-5f2d-7d98-cba424de2e74@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
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
each address for each page? Length of the VMA segment?
Physical address?
next prev parent reply other threads:[~2018-05-07 14:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 5:58 [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node information Prakash Sangappa
2018-05-02 21:33 ` Andrew Morton
2018-05-02 22:28 ` Dave Hansen
2018-05-02 23:17 ` prakash.sangappa
2018-05-03 8:46 ` Anshuman Khandual
2018-05-03 22:27 ` prakash.sangappa
2018-05-03 22:26 ` Dave Hansen
2018-05-07 23:22 ` prakash.sangappa
2018-05-08 0:05 ` Dave Hansen
2018-05-08 1:16 ` prakash.sangappa
2018-05-09 23:31 ` Dave Hansen
2018-09-12 20:42 ` prakash.sangappa
2018-09-12 20:57 ` prakash.sangappa
2018-09-14 1:33 ` Jann Horn
2018-09-14 6:21 ` Michal Hocko
2018-09-14 12:49 ` Jann Horn
2018-09-14 13:49 ` Michal Hocko
2018-09-14 18:07 ` Prakash Sangappa
2018-09-14 18:14 ` Jann Horn
2018-05-02 23:43 ` prakash.sangappa
2018-05-03 8:57 ` Michal Hocko
2018-05-03 22:37 ` prakash.sangappa
2018-05-04 11:10 ` Michal Hocko
2018-05-03 18:03 ` Christopher Lameter
2018-05-03 22:39 ` prakash.sangappa
2018-05-04 11:12 ` Michal Hocko
2018-05-04 16:18 ` Prakash Sangappa
2018-05-10 7:42 ` Michal Hocko
2018-05-10 16:00 ` Prakash Sangappa
2018-05-11 6:39 ` Michal Hocko
2018-05-04 14:57 ` Christopher Lameter
2018-05-04 16:27 ` Prakash Sangappa
2018-05-07 14:47 ` Christopher Lameter [this message]
2018-05-07 22:50 ` prakash.sangappa
2018-05-08 12:53 ` Christopher Lameter
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=alpine.DEB.2.21.1805070945200.21162@nuc-kabylake \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=prakash.sangappa@oracle.com \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).