Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp376997ybl; Fri, 23 Aug 2019 02:10:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqwSelypf6R0OFQwwAfBWKSftK1CowUaq+V+iEsZVwJTKAQqrgF3iNWJPUfRuznEUxmPtiko X-Received: by 2002:a17:90a:bb91:: with SMTP id v17mr3952892pjr.84.1566551426870; Fri, 23 Aug 2019 02:10:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566551426; cv=none; d=google.com; s=arc-20160816; b=Ij1xQpOdx/C2Dr00oCJghV2vuRE/RKR06HznGOdnFj7zfqyT39sis7lS4hutB9bhIH ieU7J6pbXY4k7h4NM6giGREGJL6ULB/AS7Vq7QUMNvpAYzksRXYrVq6VA7k0KuIMR6gG 78fMO5g9GMPYhGjEhtsVDaxj5GwerZAviRBbEaQy1BvZ+YCJDuK9msoEMfoBUPrfIl2O Fv+XjVu9M62XDdFdT6eCC2PQx0vPuorxlRZge3AXrA2VNpIqtinfoM4zT5qpcnu/HbWZ 9nnElAEISgmguk4B70qwWhAxm8zjyKVI0mQmoQfz7lXrniGwRF1Kb1Xbh/in1BdmVQRi LI7A== 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; bh=iGet9Ls/+nxGUVNaNEXT3jG3M21g/+SSiAgI6Sz3VZQ=; b=k405lbJSk2kjDoVqFEVerrcOzsenas4/L4ZlltnZ9VFW7ksFXIWz0BCM+SJm8eAobe JzsClIKBT2zYTSoiNstg28Be5o/6+REqyYqywoNZt75R012Q7vKL0v2V67OOx2UIwGeA E1NvA6GGAFbyUp1s4uiSj/wYRbzMHzmQ8JFu/0mvyoGPc1iedVi1i7Mncb9Syc57S527 aQrqCuiomKr3xeLCNCRnglM3GoTR8ukWu5Zxu70AnVEchKihj+GrNwtGYCujFZVHxhBO Yy3/qVtF7ze2XFQsbnEY1rjEZ7UT4mhJpfjtJXvYLCOqgznqMdGf9eqKqvnEFvzhXL4z 3Iaw== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v14si1831880pjb.82.2019.08.23.02.10.11; Fri, 23 Aug 2019 02:10:26 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730490AbfHWAYq (ORCPT + 99 others); Thu, 22 Aug 2019 20:24:46 -0400 Received: from mga07.intel.com ([134.134.136.100]:11269 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727377AbfHWAYq (ORCPT ); Thu, 22 Aug 2019 20:24:46 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Aug 2019 17:24:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,419,1559545200"; d="scan'208";a="173314320" Received: from iweiny-desk2.sc.intel.com ([10.3.52.157]) by orsmga008.jf.intel.com with ESMTP; 22 Aug 2019 17:24:44 -0700 Date: Thu, 22 Aug 2019 17:24:44 -0700 From: Ira Weiny To: John Hubbard Cc: Andrew Morton , Christoph Hellwig , Dan Williams , Dave Chinner , Jan Kara , Jason Gunthorpe , =?iso-8859-1?B?Suly9G1l?= Glisse , Vlastimil Babka , LKML , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-rdma@vger.kernel.org Subject: Re: [PATCH v2 0/3] mm/gup: introduce vaddr_pin_pages_remote(), FOLL_PIN Message-ID: <20190823002443.GA19517@iweiny-DESK2.sc.intel.com> References: <20190821040727.19650-1-jhubbard@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190821040727.19650-1-jhubbard@nvidia.com> User-Agent: Mutt/1.11.1 (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 20, 2019 at 09:07:24PM -0700, John Hubbard wrote: > Hi Ira, > > This is for your tree. I'm dropping the RFC because this aspect is > starting to firm up pretty well. > > I've moved FOLL_PIN inside the vaddr_pin_*() routines, and moved > FOLL_LONGTERM outside, based on our recent discussions. This is > documented pretty well within the patches. > > Note that there are a lot of references in comments and commit > logs, to vaddr_pin_pages(). We'll want to catch all of those if > we rename that. I am pushing pretty hard to rename it to > vaddr_pin_user_pages(). > > v1 of this may be found here: > https://lore.kernel.org/r/20190812015044.26176-1-jhubbard@nvidia.com I am really sorry about this... I think it is fine to pull these in... There are some nits which are wrong but I think with the XDP complication and Daves' objection I think the vaddr_pin information is going to need reworking. So the documentation there is probably wrong. But until we know what it is going to be we should just take this. Do you have a branch with this on it? The patches don't seem to apply. Looks like they got corrupted somewhere... :-/ Thanks, Ira > > John Hubbard (3): > For Ira: tiny formatting tweak to kerneldoc > mm/gup: introduce FOLL_PIN flag for get_user_pages() > mm/gup: introduce vaddr_pin_pages_remote(), and invoke it > > drivers/infiniband/core/umem.c | 1 + > include/linux/mm.h | 61 ++++++++++++++++++++++++++++++---- > mm/gup.c | 40 ++++++++++++++++++++-- > mm/process_vm_access.c | 23 +++++++------ > 4 files changed, 106 insertions(+), 19 deletions(-) > > -- > 2.22.1 > >