From: Dave Hansen <dave.hansen@intel.com>
To: prakash.sangappa@oracle.com,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-api@vger.kernel.org, mhocko@suse.com,
kirill.shutemov@linux.intel.com, n-horiguchi@ah.jp.nec.com,
drepper@gmail.com, rientjes@google.com,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Subject: Re: [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node information
Date: Thu, 3 May 2018 15:26:53 -0700 [thread overview]
Message-ID: <8569dabb-4930-aa20-6249-72457e2df51e@intel.com> (raw)
In-Reply-To: <82d2b35c-272a-ad02-692f-2c109aacdfb6@oracle.com>
On 05/03/2018 03:27 PM, prakash.sangappa wrote:
>>
> If each consecutive page comes from different node, yes in
> the extreme case is this file will have a lot of lines. All the lines
> are generated at the time file is read. The amount of data read will be
> limited to the user read buffer size used in the read.
>
> /proc/<pid>/pagemap also has kind of similar issue. There is 1 64
> bit value for each user page.
But nobody reads it sequentially. Everybody lseek()s because it has a
fixed block size. You can't do that in text.
next prev parent reply other threads:[~2018-05-03 22:26 UTC|newest]
Thread overview: 37+ 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 [this message]
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
2018-05-07 22:50 ` prakash.sangappa
2018-05-08 12:53 ` Christopher Lameter
2018-09-12 23:02 Alexey Dobriyan
2018-09-13 22:17 ` prakash.sangappa
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=8569dabb-4930-aa20-6249-72457e2df51e@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@gmail.com \
--cc=khandual@linux.vnet.ibm.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=nao.horiguchi@gmail.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).