From mboxrd@z Thu Jan 1 00:00:00 1970 From: "prakash.sangappa" Subject: Re: [RFC PATCH] Add /proc//numa_vamaps for numa node information Date: Mon, 7 May 2018 18:16:13 -0700 Message-ID: References: <1525240686-13335-1-git-send-email-prakash.sangappa@oracle.com> <20180502143323.1c723ccb509c3497050a2e0a@linux-foundation.org> <2ce01d91-5fba-b1b7-2956-c8cc1853536d@intel.com> <33f96879-351f-674a-ca23-43f233f4eb1d@linux.vnet.ibm.com> <82d2b35c-272a-ad02-692f-2c109aacdfb6@oracle.com> <8569dabb-4930-aa20-6249-72457e2df51e@intel.com> <51145ccb-fc0d-0281-9757-fb8a5112ec24@oracle.com> Reply-To: prakash.sangappa@oracle.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Dave Hansen , Anshuman Khandual , Andrew Morton 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 List-Id: linux-api@vger.kernel.org On 05/07/2018 05:05 PM, Dave Hansen wrote: > On 05/07/2018 04:22 PM, prakash.sangappa wrote: >> However, with the proposed new file, we could allow seeking to >> specified virtual address. The lseek offset in this case would >> represent the virtual address of the process. Subsequent read from >> the file would provide VA range to numa node information starting >> from that VA. In case the VA seek'ed to is invalid, it will start >> from the next valid mapped VA of the process. The implementation >> would not be based on seq_file. > So you're proposing a new /proc/ file that appears next to and is > named very similarly to the exiting /proc/, but which has entirely > different behavior? It will be /proc//numa_vamaps. Yes, the behavior will be different with respect to seeking. Output will still be text and the format will be same. I want to get feedback on this approach.