Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4752579ybi; Tue, 28 May 2019 01:51:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbB6g55/YysqQB5VTRp7SbvFbtN53ZiPOaXVdZWcDyzUN4VRDnpdAlpfG7KooYJtdcFZym X-Received: by 2002:a17:90a:9202:: with SMTP id m2mr4189536pjo.37.1559033462960; Tue, 28 May 2019 01:51:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559033462; cv=none; d=google.com; s=arc-20160816; b=MES4/G/153vVZ8CkGo/DMWYZFrUTvAKMrU4uWHvFKjQ9AQzMrCaLy+anlJRAXneQ9w 55OYQgf1vBVWpauuozuBPM3VwiX8cllW0s0aW4OyZEvKWa29Cqm3Oap+xWIcDaBd4G/c kP2h0neriEpAO7E5Ne2n9ba6jVPzjjb33erxBwimhtD0lAuM3db6Fgc85TNeNtkjp9fQ 8s0XIfRcXhbx2zA6f6PVS26BoIA2SaGLRSrRUzDBzADCWVqIRvnBagW/kc9H39J8dFCh ycH1jKUA3/YWOwkB2bida+Ze7n3lesRm/fCd5cncqg1x7s3ldb2A1y8a6AcBHdGlT6dX wQ/w== 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:dkim-signature; bh=yyUeiuvEAPZA604X3Qsle66wGTeITptdd2/mkPm2vyI=; b=s3Qydel60wxTNg4r1e0VYeiQJhmmhdwJh42cl636iatK1uJ/B12rW1T77tuNOKWJC6 D2Ol+AIB8kySpsEWu1B7rv4K+FeH+b8QkYlYWtASLRIXX6Zxy1ah9HIQ5kGE+A2Jmo/0 M1mnOAgenAtXmqLQJ1hlzZlNmXNBXbWAZYN0lUzMoWaFNp7Px2t5+lRsXGwxDTFHrqh0 ZxYvB+z4Bo2540+L5CpuzutrU2koyyEbEmBfAJBvxS6ZjfeyTVEcSfYyCMH+d/1bgvBt vr1/UTcm8ORvoL6t3rODGnAZZMyWHYINxwFoAfl4HJ1Ztr/UDMpV+KmlI2fUfljRgW+r BKng== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b="GUdtm2Y/"; 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 d62si21161181pga.447.2019.05.28.01.50.45; Tue, 28 May 2019 01:51:02 -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; dkim=fail header.i=@gmail.com header.s=20161025 header.b="GUdtm2Y/"; 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 S1726538AbfE1Itf (ORCPT + 99 others); Tue, 28 May 2019 04:49:35 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:44035 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725943AbfE1Itf (ORCPT ); Tue, 28 May 2019 04:49:35 -0400 Received: by mail-pg1-f194.google.com with SMTP id n2so10551455pgp.11; Tue, 28 May 2019 01:49:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=yyUeiuvEAPZA604X3Qsle66wGTeITptdd2/mkPm2vyI=; b=GUdtm2Y/xH530GIsF7hKD2bjE7d4L/YyedgUu6O7oznl9DqX84dH45WsG3vgu2VtMx 4esY7XbmjbBgpNICqEtwGvORDOMOdigx6H6ThgY07VYfInU+DPQ+lx06LqXlKAI960cq LBVfzXpwEGX7+S5jPsc5h5emULZqdWjrECLRaTbhGaZsBkDU9ExuwWE5VO04YIqZXERo 0recf4DhGEakwNR0o8N9+YSS9djGhhhmSUYV7hCm14r4yEI/gAvn0+q6YIzBefHgVbE5 7UoC2lhWEPJ0ZG1KSZUv1tTaT4tJ6WC5p5Lnmt3MAlJ/7Uk28QlzIn5ICuyg/n7FJUQv OhGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=yyUeiuvEAPZA604X3Qsle66wGTeITptdd2/mkPm2vyI=; b=bwu55jVebWiFtTH+WoJ7SkL2k7xT/874Lc1TcO2bicBU2hB0nWWPOdy0qhwGkBEYmQ IrcJebalPi4wT5kric/A50CID0U04Q62qwJjUCQOqNVpx7W/IpTVw/BbaKXzQQMprAYd Fvj+CB0dlvv4uYpILkpp2gXitm+6rrIoXEdCqbXdRWv11009ZHu9CK32Qw7Mk+vdXDX/ YtrsCgSHSuTrjEvPq5AejU7zYT1JA1ZbE30sVYa0Ga2JQQAzH+31y8N1nU7+uc/mcg9D 7OWtAWddJdIGMTxC9Yb8Vo+nvcY2kyIFzcJbUBa9AW04DawGEDzUHsRdxuIaOwrz+TYZ GMRw== X-Gm-Message-State: APjAAAUQeIGRsxByc22OzZO5oZmCBlypG1DjHZnNUOGeQhSjncG8/iXS qb9/iNLGyH+x3/cSJPcXfdM= X-Received: by 2002:a62:4dc5:: with SMTP id a188mr90994883pfb.8.1559033374062; Tue, 28 May 2019 01:49:34 -0700 (PDT) Received: from google.com ([2401:fa00:d:0:98f1:8b3d:1f37:3e8]) by smtp.gmail.com with ESMTPSA id d19sm1694790pjs.22.2019.05.28.01.49.29 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 28 May 2019 01:49:32 -0700 (PDT) Date: Tue, 28 May 2019 17:49:27 +0900 From: Minchan Kim To: Daniel Colascione Cc: Michal Hocko , Andrew Morton , LKML , linux-mm , Johannes Weiner , Tim Murray , Joel Fernandes , Suren Baghdasaryan , Shakeel Butt , Sonny Rao , Brian Geffon , Linux API Subject: Re: [RFC 7/7] mm: madvise support MADV_ANONYMOUS_FILTER and MADV_FILE_FILTER Message-ID: <20190528084927.GB159710@google.com> References: <20190520035254.57579-8-minchan@kernel.org> <20190520092801.GA6836@dhcp22.suse.cz> <20190521025533.GH10039@google.com> <20190521062628.GE32329@dhcp22.suse.cz> <20190527075811.GC6879@google.com> <20190527124411.GC1658@dhcp22.suse.cz> <20190528032632.GF6879@google.com> <20190528062947.GL1658@dhcp22.suse.cz> <20190528081351.GA159710@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 28, 2019 at 01:31:13AM -0700, Daniel Colascione wrote: > On Tue, May 28, 2019 at 1:14 AM Minchan Kim wrote: > > if we went with the per vma fd approach then you would get this > > > feature automatically because map_files would refer to file backed > > > mappings while map_anon could refer only to anonymous mappings. > > > > The reason to add such filter option is to avoid the parsing overhead > > so map_anon wouldn't be helpful. > > Without chiming on whether the filter option is a good idea, I'd like > to suggest that providing an efficient binary interfaces for pulling > memory map information out of processes. Some single-system-call > method for retrieving a binary snapshot of a process's address space > complete with attributes (selectable, like statx?) for each VMA would > reduce complexity and increase performance in a variety of areas, > e.g., Android memory map debugging commands. I agree it's the best we can get *generally*. Michal, any opinion?