Received: by 10.192.165.148 with SMTP id m20csp3674802imm;
        Mon, 7 May 2018 17:06:45 -0700 (PDT)
X-Google-Smtp-Source: AB8JxZoWFk7glRgFdpfAcqAYpDNIavR6LHKVhSTqPu2HqnC1YB70AfvrDl69DO5IWBuKVWdSlp/E
X-Received: by 10.98.110.136 with SMTP id j130mr37481185pfc.111.1525738004938;
        Mon, 07 May 2018 17:06:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1525738004; cv=none;
        d=google.com; s=arc-20160816;
        b=HM8GnGBTNGGI3WisyzqAR1sUMSScFLEseeIKSze2eYz+yGLCSO/l/XBMcOFN9KD0hQ
         9F9LiQvBWOvmFY098qUZEnpC0YcjAlOuaSkB8o7xB54M+7JjoRFtYNOdg2AELv647pU3
         mYp7UPE6BrXfLlMwGQfh46mDYg9rRoNWG9I25xrXlomT62kRwfQYBqJAoi/3X2oZna9e
         ay3I6yo/6Nz3YhnOcVzJ1BhjlaOos20Y1jdmENPQizpffpduuCnP7qH2VllgJN368H1T
         dW0w4qCSSgXzIQjZB5rQP52QaHiVH3o+IIg1V5MWWhiNLs5njbQNfHZ2eidhxJk4pxvq
         5G5Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:content-transfer-encoding
         :content-language:in-reply-to:mime-version:user-agent:date
         :message-id:openpgp:from:cc:references:to:subject
         :arc-authentication-results;
        bh=GbUURFUHuBpSuSdnmFCgJLsdMX3lchhu2opxmwq7c0w=;
        b=PCdT4mym9YAMj11thVAUTVnHNnBg/U3QBzcnjV+cLlh0OQBC9o8sNSclLBlowgxNR0
         xSEG1sf4qM2w0wv3mxScwci4GezPV5vO0PuYbsckXjvONqyemwuJt8OUsDAZHBwxwCWb
         R40Ya5LhOIgFCkaX4RlbDf1EggQtcrI+1uqAKxtecVkeYK+6LKt+TFdi1wZG3hzKOtGG
         5Hm1iVx5i3jbSn+61/ksdcEoMwf1t6/B6QwgyYBle9xsAk05m6NRIlTVzvcB2D/EB4wg
         Gc8mJSIoKL2zezHzflkmoTYHCnICMRpvYwXQCobh0510ZiU+k4sSsugSlpaKRwXWOTy0
         1pKw==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id g1-v6si12136941pgq.597.2018.05.07.17.06.30;
        Mon, 07 May 2018 17:06:44 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Authentication-Results: mx.google.com;
       spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753505AbeEHAFq (ORCPT <rfc822;hououinredflag@gmail.com>
        + 99 others); Mon, 7 May 2018 20:05:46 -0400
Received: from mga06.intel.com ([134.134.136.31]:36957 "EHLO mga06.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752848AbeEHAFp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 7 May 2018 20:05:45 -0400
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga006.jf.intel.com ([10.7.209.51])
  by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 May 2018 17:05:44 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.49,376,1520924400"; 
   d="scan'208";a="40003022"
Received: from ray.jf.intel.com (HELO [10.7.201.133]) ([10.7.201.133])
  by orsmga006.jf.intel.com with ESMTP; 07 May 2018 17:05:44 -0700
Subject: Re: [RFC PATCH] Add /proc/<pid>/numa_vamaps for numa node information
To:     prakash.sangappa@oracle.com,
        Anshuman Khandual <khandual@linux.vnet.ibm.com>,
        Andrew Morton <akpm@linux-foundation.org>
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>
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>
From:   Dave Hansen <dave.hansen@intel.com>
Openpgp: preference=signencrypt
Message-ID: <c72fea44-59f3-b106-8311-b5eae2d254e7@intel.com>
Date:   Mon, 7 May 2018 17:05:44 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <51145ccb-fc0d-0281-9757-fb8a5112ec24@oracle.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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/<pid> file that appears next to and is
named very similarly to the exiting /proc/<pid>, but which has entirely
different behavior?