Received: by 10.192.165.148 with SMTP id m20csp646656imm; Fri, 4 May 2018 04:12:52 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoRdIlhqxN9E467O/mKrxnf1NMvEN23tNayeU67MSvZBzjHh45jw53xauagTBbjC21vZaoe X-Received: by 2002:a63:7e09:: with SMTP id z9-v6mr22422358pgc.437.1525432372438; Fri, 04 May 2018 04:12:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525432372; cv=none; d=google.com; s=arc-20160816; b=ieiYxVR1dMFSaGcK+JRSXVtcjCsF8FTvm0krg34j9r0Ootfi5XmSRuKUIkxVg6RHs+ bqRenEWFGaMddwA0Hl3AfpisUTtyZ9BQ1yt4xIF0/10C/S0XDZfbcyKo8EbvOnWfYjH1 S+q4qbzjBIi//Gqsu3dsozEzhyxiyRz+ZwcWHCvzdx6gM6zeih2J3cic8avwfHmMa3nv a3OrNnGffUOAbxv9DWyjIq7AIkeL81axbIrtl5QbHuZtjcpbOFCylsUdg3Htw9mh3PnU GupRTP6bjeV4MLiW22Bc43PbiW6a1qA8Oa21NyTkAOHKNTOrBg21PvgJFmWrny5jWe3I 5Eig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=Gl3TphsxwQvdFDGjxMmUzsxzVCjueSJuFC0HcQN+n8Y=; b=YA0m8+zIjQ7Y/lRX/brH3+QMhIgg9l4zghRt/d3Uj1ZFJuw/IbbCi1i526h5O9qOgH 8nXhu6+gKjFIXWwa+xWOcUF34VEIs2Of+IU8qwPiZQLoovka0wx2gs9RMYFcgyZ8uH30 m/yJES4Yqafmet2927sCWOQ4hR3Z750rq5PLK4sMVBgMRy90ofYCZknop8FcwDw9S8ZJ ySV+MRd4TS/qaYmWNOC4PyK6FcGXFbsKKWIZFZe6zZFFfvtqd54BgU5xB4iZFmlzKVNC fLlcU4ebHhHZeIMZo3cysuYQQrIU1ok0U47s92yHJvlR4GJX+klL4twascNrW+p9zIU4 B4Lw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j61-v6si15607777plb.317.2018.05.04.04.12.38; Fri, 04 May 2018 04:12:52 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751346AbeEDLMQ (ORCPT + 99 others); Fri, 4 May 2018 07:12:16 -0400 Received: from mx2.suse.de ([195.135.220.15]:49201 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751106AbeEDLMP (ORCPT ); Fri, 4 May 2018 07:12:15 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 1C816AB3E; Fri, 4 May 2018 11:12:14 +0000 (UTC) Date: Fri, 4 May 2018 13:12:11 +0200 From: Michal Hocko To: "prakash.sangappa" Cc: Christopher Lameter , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-api@vger.kernel.org, akpm@linux-foundation.org, 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 Message-ID: <20180504111211.GO4535@dhcp22.suse.cz> References: <1525240686-13335-1-git-send-email-prakash.sangappa@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 03-05-18 15:39:49, prakash.sangappa wrote: > > > On 05/03/2018 11:03 AM, Christopher Lameter wrote: > > On Tue, 1 May 2018, Prakash Sangappa wrote: > > > > > For analysis purpose it is useful to have numa node information > > > corresponding mapped address ranges of the process. Currently > > > /proc//numa_maps provides list of numa nodes from where pages are > > > allocated per VMA of the process. This is not useful if an user needs to > > > determine which numa node the mapped pages are allocated from for a > > > particular address range. It would have helped if the numa node information > > > presented in /proc//numa_maps was broken down by VA ranges showing the > > > 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. yes we have. See move_pages... > > > 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. Well, that breaks the layout randomization, doesn't it? -- Michal Hocko SUSE Labs