Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2112533rwd; Fri, 26 May 2023 01:44:49 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6pv6HcKnQHqJt0ZKw1OoFIdpQuM0hsIRiTUQx3eN8N4LudZVgkFkKOCYUuosJlE7H2aCeh X-Received: by 2002:a17:902:e54f:b0:1a6:bd5c:649d with SMTP id n15-20020a170902e54f00b001a6bd5c649dmr2702996plf.56.1685090688975; Fri, 26 May 2023 01:44:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685090688; cv=none; d=google.com; s=arc-20160816; b=JdRb1jxpsFBpEsTK/1O8OiMRrad8K4TJbJvew3x4kv+oG3+wH7ljvct/P2t7pCXfn0 cgqpCZCKsg2c5+kXTAuWBlCHD83Z9X11C32MN1MDO2lBL6tdNkmcwFd6pBmrzRLk1G22 ROONsTQtcr69ZeLG0rqo+kQzh6IaJBUOtTGrBS1kIcae/NGVyM3Uy3LNqxx7yj9cgp0f +xDmTWbeR4WLnipDwIGgflN0wLJGzUXPlFjtG+M81g29H5Bv3PHXEO6GVybnMkfTnXBq 66nOt9EdCvrFytWdLyaEyKoUXsZz+MdLmZXLs/xAqgoDyWnYXBKckJQbonK/xvuaaXZJ pryw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-id:mime-version:subject :cc:to:references:in-reply-to:from:organization:dkim-signature; bh=9x40KdygSXIWGnbkte2M+HVRzUVagP25yP4BkTs6dKs=; b=gMJtuTfZH83C3FNS5gnXL68QG9cnPS6+6pjM29v3z59PMUgmpnz12l+pqT+GvC0sIP FhFhHlPfRmIn4mTentKpbBzWMPBsG77pdDLsY/GGidtCTuTCa1hl4NEreSCzOsvGrYyR 9Lrlb3VOLoAm8htlhLaXs2cMmDxe0NcAg6ZcA68UOzeJDNgLE9D+hQ5zHUJBd+GeuN8v DSxCZrEfWjyXRqueFAejI9X7N5aoe208I5IFuMnNY8u56lXKrYN51ekshnryVD1jRuc4 5lgE7DMoqAUvbSppYz04ZL/YVaCLzfV2UWpRkQDC3uhx8QR5A+cpLg0eRrHJnoTEurru 4oQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=V7tcJSgz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i11-20020a17090a65cb00b0024e184e5a53si3521771pjs.117.2023.05.26.01.44.37; Fri, 26 May 2023 01:44:48 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=V7tcJSgz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242655AbjEZIcZ (ORCPT + 99 others); Fri, 26 May 2023 04:32:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236911AbjEZIcY (ORCPT ); Fri, 26 May 2023 04:32:24 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 62DCFD8 for ; Fri, 26 May 2023 01:31:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1685089899; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=9x40KdygSXIWGnbkte2M+HVRzUVagP25yP4BkTs6dKs=; b=V7tcJSgzEWC5Mh+AZHZAMqivhnJgMXiCcD2Vt2splEBzFHAF2IsOli6oBu4Sfhj7l2fJaw 2ZOdpa+Ze0Ctcz5it2ADGGbudz4OTMIEq2hUoDEsB+HXwuMxbRpwM7w+n5motfNIDzx+bk rz83MZ/7+w1b0yPZr54LYlE52B68mHA= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-56-uWGuQWl-PUm_FXH94Jwp5A-1; Fri, 26 May 2023 04:31:34 -0400 X-MC-Unique: uWGuQWl-PUm_FXH94Jwp5A-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2612085A5AA; Fri, 26 May 2023 08:31:33 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.39.192.68]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5E584200AD47; Fri, 26 May 2023 08:31:30 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <20230525223953.225496-1-dhowells@redhat.com> <20230525223953.225496-3-dhowells@redhat.com> To: Christoph Hellwig Cc: dhowells@redhat.com, David Hildenbrand , Jens Axboe , Al Viro , Matthew Wilcox , Jan Kara , Jeff Layton , Jason Gunthorpe , Logan Gunthorpe , Hillf Danton , Christian Brauner , Linus Torvalds , linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton Subject: Re: [RFC PATCH v2 2/3] mm: Provide a function to get an additional pin on a page MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <520384.1685089889.1@warthog.procyon.org.uk> Date: Fri, 26 May 2023 09:31:29 +0100 Message-ID: <520385.1685089889@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christoph Hellwig wrote: > > +void page_get_additional_pin(struct page *page) > > page_get_additional_pin seems like an odd name, mixing the get and > pin terminologies. What about repin_page? I considered that, though repin_page() suggests putting a pin back in after one is removed, but I can go with that if no one objects. > Or move to a folio interface from the start can call it folio_repin? I also considered this, but the entire gup interface is page-based at the moment, but I can do that too:-/ David