Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp785577pxk; Mon, 31 Aug 2020 00:18:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzLHtj9+jazElg4mTXOWw/dUtAV4i/8FEKdn6IRuTAhkrttQQtXbhYG6bxCJ2GM3JzNqqPs X-Received: by 2002:a17:906:7d16:: with SMTP id u22mr10577951ejo.176.1598858284562; Mon, 31 Aug 2020 00:18:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598858284; cv=none; d=google.com; s=arc-20160816; b=QbL3wqSY4Yt5sMKL09DFAcZgfN5wnngjYnlSXtcV3oykgFEMUaF20MrlR+iTaZLQBX h8OwDDwsTvfLpUAkyOH1IllH8tW9T6PtVzUeXuxxrq/KrD710lgKonCKQiDLLKaIn4V8 R7dwWa+IFiXNV/ox9qR8uiCL6CfPlk8FIsA7pwOiCMj0GLNVTTgI2XvOA8uQ7/vOqLVo DZnz9YV1sxk3VoxU30CRP6AAqtcOO/iLEueeSYSllrZKgO3Nu/r722G9rowyhy8YJF0B kCD2DEr9LWVoyl13FUSbLYGs/RwgBxinjPzEoB9uc5rYO4M/gjkuHid/QAbt2VRDwEeG caAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :mime-version:references:in-reply-to:message-id:date:subject:cc:to :from; bh=g/hUeZFRhmcyiBdywMfjY5hsszErlS3vn8kKwBqUBqw=; b=sXaNaFRC4PIKfcfomjTbHSgBwMBkPxossedKMxoLKnlAV10zZSqgXQ1m0l7mACNuSa zN34wgQY8BURuAADn8ZdDjQzD7JRYtozYMKtCga3H6FxEE7fAr84sdNse8wvc9BJEU9x EjDJx+JzyHbU5iuKvFSupaV8nQeC33TfhwGzw3NT5YojmpAA2O60JKdtwIKxRDygNkvr /bMsllAEfP5wOQCWfD6Ygz8Y8zPx5ZtIczorHHW+JGSJ5F4lHNav7Thf7EokhfG5SzOY HEHAwjhJn6hiqFqhbcBx9N9ZI3GT9lweFmST506KmYYOcjnv8BtnHuIv59AQ4RITyhAm UMkA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=kjUinpiM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hh13si4978156ejb.706.2020.08.31.00.17.41; Mon, 31 Aug 2020 00:18:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=kjUinpiM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728035AbgHaHO5 (ORCPT + 99 others); Mon, 31 Aug 2020 03:14:57 -0400 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:16659 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727883AbgHaHOs (ORCPT ); Mon, 31 Aug 2020 03:14:48 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 31 Aug 2020 00:12:40 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 31 Aug 2020 00:14:46 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 31 Aug 2020 00:14:46 -0700 Received: from HQMAIL109.nvidia.com (172.20.187.15) by HQMAIL111.nvidia.com (172.20.187.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 31 Aug 2020 07:14:46 +0000 Received: from rnnvemgw01.nvidia.com (10.128.109.123) by HQMAIL109.nvidia.com (172.20.187.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 31 Aug 2020 07:14:45 +0000 Received: from sandstorm.nvidia.com (Not Verified[10.2.61.194]) by rnnvemgw01.nvidia.com with Trustwave SEG (v7,5,8,10121) id ; Mon, 31 Aug 2020 00:14:45 -0700 From: John Hubbard To: Andrew Morton CC: Alexander Viro , Christoph Hellwig , Ilya Dryomov , Jens Axboe , , , , , LKML , John Hubbard Subject: [PATCH v3 1/3] mm/gup: introduce pin_page() Date: Mon, 31 Aug 2020 00:14:37 -0700 Message-ID: <20200831071439.1014766-2-jhubbard@nvidia.com> X-Mailer: git-send-email 2.28.0 In-Reply-To: <20200831071439.1014766-1-jhubbard@nvidia.com> References: <20200831071439.1014766-1-jhubbard@nvidia.com> MIME-Version: 1.0 X-NVConfidentiality: public Content-Transfer-Encoding: quoted-printable Content-Type: text/plain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1598857960; bh=g/hUeZFRhmcyiBdywMfjY5hsszErlS3vn8kKwBqUBqw=; h=X-PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer: In-Reply-To:References:MIME-Version:X-NVConfidentiality: Content-Transfer-Encoding:Content-Type; b=kjUinpiMx6nsErCxVCskj43Z3DmEoRKcD9i9ivUNEYiZZUvdAQHLzGVFbnxLz5nhr gU9ZVgqVz0+ENK96+ymx5ri0Qu3f+reKGD4pt8qDZjXFXqVIl2GN2MtTQIV46VD7l0 vRRZcwo3jXjvLR6MZCdGCc/SD7/QCWrvHe3XFUal/qZtcgTs7Auk+30WD6C3NRO8so J9oszswXn1+MED+pJTlgHtKokzefEkarkTGqOpWg6hOtomvqMdvyLTH8W5VoHDFKQu zMwxsVRna0Ka+n9/VhYUUDZeT8gnPNL2ZwT/7z2QMTYjoIHFeLcUfmvIMNZpQdS46R VQuBC2Om1nakw== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org pin_page() is the FOLL_PIN equivalent of get_page(). This was always a missing piece of the pin/unpin API calls (early reviewers of pin_user_pages() asked about it, in fact), but until now, it just wasn't needed. Finally though, now that the Direct IO pieces in block/bio are about to be converted to use FOLL_PIN, it turns out that there are some cases in which get_page() and get_user_pages_fast() were both used. Converting those sites requires a drop-in replacement for get_page(), which this patch supplies. [1] and [2] provide some background about the overall effort to convert things to pin_user_page*() and unpin_user_page*(). [1] "Explicit pinning of user-space pages": https://lwn.net/Articles/807108/ [2] Documentation/core-api/pin_user_pages.rst Cc: Christoph Hellwig Signed-off-by: John Hubbard --- include/linux/mm.h | 2 ++ mm/gup.c | 33 +++++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+) diff --git a/include/linux/mm.h b/include/linux/mm.h index ca6e6a81576b..24240cf66c44 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -1154,6 +1154,8 @@ static inline void get_page(struct page *page) page_ref_inc(page); } =20 +void pin_page(struct page *page); + bool __must_check try_grab_page(struct page *page, unsigned int flags); =20 static inline __must_check bool try_get_page(struct page *page) diff --git a/mm/gup.c b/mm/gup.c index ae096ea7583f..a3a4bfae224a 100644 --- a/mm/gup.c +++ b/mm/gup.c @@ -123,6 +123,39 @@ static __maybe_unused struct page *try_grab_compound_h= ead(struct page *page, return NULL; } =20 +/* + * pin_page() - elevate the page refcount, and mark as FOLL_PIN + * + * This the FOLL_PIN equivalent of get_page(). It is intended for use when= the + * page will be released via unpin_user_page(). + * + * Unlike pin_user_page*(), pin_page() may be used on nearly any page, not= just + * userspace-allocated pages. + */ +void pin_page(struct page *page) +{ + int refs =3D 1; + + page =3D compound_head(page); + + VM_BUG_ON_PAGE(page_ref_count(page) <=3D 0, page); + + if (hpage_pincount_available(page)) + hpage_pincount_add(page, 1); + else + refs =3D GUP_PIN_COUNTING_BIAS; + + /* + * Similar to try_grab_compound_head(): even if using the + * hpage_pincount_add/_sub() routines, be sure to + * *also* increment the normal page refcount field at least + * once, so that the page really is pinned. + */ + page_ref_add(page, refs); + + mod_node_page_state(page_pgdat(page), NR_FOLL_PIN_ACQUIRED, 1); +} + /** * try_grab_page() - elevate a page's refcount by a flag-dependent amount * --=20 2.28.0