Received: by 10.192.165.148 with SMTP id m20csp140836imm; Fri, 4 May 2018 07:59:33 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoWjx9vrhDlkOIwkxt4LuTciLUyR6tngEGo0uMTQRW6OYSK7MHScd8xKaafHmrg2NStQnIv X-Received: by 2002:a63:9711:: with SMTP id n17-v6mr22179998pge.171.1525445973079; Fri, 04 May 2018 07:59:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525445973; cv=none; d=google.com; s=arc-20160816; b=wAouALGvulnAYwOthlTipt8OrWjyTO5M1ILpAqy29zz2Bb3BZuPoHjBbaR/DYj6KNB 0Y950Sjm0e9TspgFZep4deZw8vZP/GaAPeY00//oiOETBjh2Wg6zyFGk/muVEHSwP52G QtbAvYGy2HBOFouGnDZGFGSNwmqe0KW8Vpvlv4QJ9ympMjpzwTwPU1jWmJU9B/6FbiQz 9ZUHmcXkOrl8SGgPlIzxYYQBMAxq4euFB5dBKU7CDA/uvi68VGOhBwtRZCTvnPmRbEtc pTBSEkRWLzpobYOEtW2ARL1J/oYxf6sIEDwvlta0hLyDW45ShQ3DMnMaL+iKSsjojwqJ 1/oQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=HsCf33pJq0TkwBJPWtlF5HjAdOgpsJK9uLBMhR06Bsw=; b=vwANU/UF/62GHTpeUhiZc0h4geoyzPiSydgqYGRupUYkUiHmN2yuKUDGW5l0MdggvF VQyDVl9qy9QoxkIirmBHrMjexz+jxMMqaBJK1QiCXj/xEpGhtHqiocAbstjvgK+qM5sE 9bGLRI3o+phFi7bJYf7LayCcGFs1Adit5V8qI9HoqVoDkcEhkwffFPdJUmnD4e2+uXDP /S4357VmCZ1q+cTKKJ6sECB0O5Qk6lpCtt531pTqs1I0AZ9j9ilLVf8yFDCvlge+jb2M yiCHlZfB9pubxoROn+tb09aHXgzCSSsC8udEiRAXU9PQEZo+o0Px/U2XlNKKzLRpjuNg +r7A== 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: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 68-v6si15959331pla.452.2018.05.04.07.59.18; Fri, 04 May 2018 07:59:33 -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 S1751412AbeEDO55 (ORCPT + 99 others); Fri, 4 May 2018 10:57:57 -0400 Received: from resqmta-po-11v.sys.comcast.net ([96.114.154.170]:42564 "EHLO resqmta-po-11v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750820AbeEDO54 (ORCPT ); Fri, 4 May 2018 10:57:56 -0400 Received: from resomta-po-19v.sys.comcast.net ([96.114.154.243]) by resqmta-po-11v.sys.comcast.net with ESMTP id EbPsfRs8AJA8JEc9kfFFuc; Fri, 04 May 2018 14:57:56 +0000 Received: from gentwo.org ([98.222.162.64]) by resomta-po-19v.sys.comcast.net with ESMTPA id Ec9ifvE0zqPQQEc9jfq6Ws; Fri, 04 May 2018 14:57:56 +0000 Received: by gentwo.org (Postfix, from userid 1001) id C83A11161682; Fri, 4 May 2018 09:57:54 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by gentwo.org (Postfix) with ESMTP id C59C61161679; Fri, 4 May 2018 09:57:54 -0500 (CDT) Date: Fri, 4 May 2018 09:57:54 -0500 (CDT) From: Christopher Lameter X-X-Sender: cl@nuc-kabylake To: "prakash.sangappa" 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//numa_vamaps for numa node information In-Reply-To: Message-ID: References: <1525240686-13335-1-git-send-email-prakash.sangappa@oracle.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfKvdZldehWcAmSyTKkxzqPGkHq0l7Z3QFh3oJuvqKcN9rFnGsr0rIMxr9Vw3fNVoWRO0FsdFxKxHs87RSSYMUXmW+oW7Gi51KE4Zk/mUCEuRJkSbRP8O eatn8aDv2NEmYt8GDCmniJAjTbYJrTQ5wAzfGhWRaX9I0EbCYlTUa+6q7caDp/xCC4kcSyymheiPtg3GHUkyTsrdOTpWyYHDijzLmyG+RuIlkZrRVFzqT3OM bNtsIEqbqFu/qejQ2Uq9A5xWcd0O23gEMdVMIdhSQsXkUrOmbf+6iN79p9336Vwl72emmqsCVF/qDLUEK0hlmrjMPj3P2ZZrbctJcr+qmrQop2vIK/JRBdVC GuZHlRToBj0gUWkOXWnZFtd5AMOAOC97WwDVdSVjU6sllYMD3BJ2bvYA9o63jySTvQ03qC2K/T+rZqKMYdcJf5sjb+koKOAwhkFriYIi0Do44ONlG7sJylh5 Dx4bi7MbFceeUN8Q Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 3 May 2018, prakash.sangappa wrote: > > > exact numa node from where the pages have been allocated. > > Cant you write a small script that scans the information in numa_maps and > > then displays the total pages per NUMA node and then a list of which > > ranges have how many pages on a particular node? > > Don't think we can determine which numa node a given user process > address range has pages from, based on the existing 'numa_maps' file. Well the information is contained in numa_maps I thought. What is missing? > > > reading this file will not be restricted(i.e requiring CAP_SYS_ADMIN). > > So a prime motivator here is security restricted access to numa_maps? > No it is the opposite. A regular user should be able to determine > numa node information. That used to be the case until changes were made to the permissions for reading numa_maps.