Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp657014ybl; Fri, 16 Aug 2019 01:48:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqxs/orvymvMdJMuQx+za6Nk3/xLR51AfT8PCzlDRgBcdGum+U16YPBHtnja+HVmQrH/6Y3b X-Received: by 2002:a17:90a:8b98:: with SMTP id z24mr6170539pjn.77.1565945302180; Fri, 16 Aug 2019 01:48:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565945302; cv=none; d=google.com; s=arc-20160816; b=Eb5BBVBjFydYmVQaxaCMm5e1L2WU0L2bzW9KoYlhjBu+CI+zIAvv8M+6TZKKcn+Oep enrJi0OsX9qKb8dChJvixbsCccNQr9Uqpm0oMq2pMqf3qxOqaYElZ8y01Jq2k3QWuq96 /z2zrYX624XBEkneQlTPva0kiylLVzzK+HEn3h4gdkrvpntUFMInrjFF/sRO6GMbQCdz gTR3OEuDMNixdhoWbCvFyCJVd9ZT6/D9cCoUP4e46KV8DsM6RrvHQgVr6wDwcNO0Fzq4 65E1QmndCKL7FRh9T8VIbBiQoq9gBox7qIXJwCOYZkThZpoxWEmaS8VNzxP5ESUbLadf H7Ug== 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:from:references:cc:to:subject; bh=QT4PxMvXtV86UGmBztzjHlx8tbz2BJoz3Idp781yKng=; b=ZH0sBuy69kvYt9DIJZoYC0LhMzvY8w/CodPM4xNUbLtarWVhzAw+dhVANgOa9qaRlg hj8vWbl9mlGaz3WuTopHtAmNyjr8ulFgIfF8vrFxC3diDrCNOf6O4TxEJ8JlHtUVWS6R PMV85qbWpGztfkl+m0xhm8b27uKG5IJXfLg94EqFVNEjRiau+ekG/sNmddmICcpg9Pp4 hwVLLCwn8e0lwKL6s/ZLxinItahH338WEbAwCQl3vxZDvtmsLRO8COX0J83jCxzR5/AH GqF6ppmr/n5p4LqLNzEPo31g8076gqPpvFQN+cAm4BBfWDadEGW8jjqkn+Hbpi82yYq3 mV8g== 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 n23si3629455plp.273.2019.08.16.01.48.04; Fri, 16 Aug 2019 01:48:22 -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 S1726967AbfHPIrZ (ORCPT + 99 others); Fri, 16 Aug 2019 04:47:25 -0400 Received: from mx2.suse.de ([195.135.220.15]:47690 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726872AbfHPIrZ (ORCPT ); Fri, 16 Aug 2019 04:47:25 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 8416CB06B; Fri, 16 Aug 2019 08:47:23 +0000 (UTC) Subject: Re: [RFC PATCH 2/2] mm/gup: introduce vaddr_pin_pages_remote() To: Jan Kara , John Hubbard Cc: Ira Weiny , Andrew Morton , Christoph Hellwig , Dan Williams , Dave Chinner , Jason Gunthorpe , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , LKML , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-rdma@vger.kernel.org References: <20190812015044.26176-3-jhubbard@nvidia.com> <20190812234950.GA6455@iweiny-DESK2.sc.intel.com> <38d2ff2f-4a69-e8bd-8f7c-41f1dbd80fae@nvidia.com> <20190813210857.GB12695@iweiny-DESK2.sc.intel.com> <90e5cd11-fb34-6913-351b-a5cc6e24d85d@nvidia.com> <20190814234959.GA463@iweiny-DESK2.sc.intel.com> <2cbdf599-2226-99ae-b4d5-8909a0a1eadf@nvidia.com> <20190815132622.GG14313@quack2.suse.cz> <20190815133510.GA21302@quack2.suse.cz> From: Vlastimil Babka Message-ID: <0d6797d8-1e04-1ebe-80a7-3d6895fe71b0@suse.cz> Date: Fri, 16 Aug 2019 10:47:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190815133510.GA21302@quack2.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/15/19 3:35 PM, Jan Kara wrote: >> >> So when the GUP user uses MMU notifiers to stop writing to pages whenever >> they are writeprotected with page_mkclean(), they don't really need page >> pin - their access is then fully equivalent to any other mmap userspace >> access and filesystem knows how to deal with those. I forgot out this case >> when I wrote the above sentence. >> >> So to sum up there are three cases: >> 1) DIO case - GUP references to pages serving as DIO buffers are needed for >> relatively short time, no special synchronization with page_mkclean() or >> munmap() => needs FOLL_PIN >> 2) RDMA case - GUP references to pages serving as DMA buffers needed for a >> long time, no special synchronization with page_mkclean() or munmap() >> => needs FOLL_PIN | FOLL_LONGTERM >> This case has also a special case when the pages are actually DAX. Then >> the caller additionally needs file lease and additional file_pin >> structure is used for tracking this usage. >> 3) ODP case - GUP references to pages serving as DMA buffers, MMU notifiers >> used to synchronize with page_mkclean() and munmap() => normal page >> references are fine. IMHO the munlock lesson told us about another one, that's in the end equivalent to 3) 4) pinning for struct page manipulation only => normal page references are fine > I want to add that I'd like to convert users in cases 1) and 2) from using > GUP to using differently named function. Users in case 3) can stay as they > are for now although ultimately I'd like to denote such use cases in a > special way as well... So after 1/2/3 is renamed/specially denoted, only 4) keeps the current interface? > Honza >