Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2322229ybc; Wed, 13 Nov 2019 12:31:56 -0800 (PST) X-Google-Smtp-Source: APXvYqxLy2epM28iDUjTRjlkVgg6sl0wPCi9PjaYTucuHX2B/WFyk6HTLxPrOBKe76nTnfBMFp8i X-Received: by 2002:aa7:d1c2:: with SMTP id g2mr5934351edp.164.1573677116091; Wed, 13 Nov 2019 12:31:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573677116; cv=none; d=google.com; s=arc-20160816; b=duK6FIIx7O2SBj5xj6MHase3gJqXSzBBuqJPASaMH3KOhMiZ5MDN2mHjHiA7DvuDPz DMWMkG5jIUQfO8513CFpE8NL0ibuajTWBjGT5piMfLx71XYGep/6h7rV1CCpQ+IYwphr 3aQ/fl5pqUibniN5Ht4LRRGYiBuUxcyVB+iUdw6CQTdUATGkYrTdwp3kKwgl/jejMdYz drs3Rk+VA3YfBUzUUfyYMIeb5J+bmVhfrjKZgsn5d/NlRr0lU8KHZzSP/vs6gPBsxR72 JGk/U/8jPjMShk61Qa9psRM/OXL9/eDCTXnrTdJHg8L/1p+eQATpSfnxlZIIN4sUMc48 SQdA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject; bh=w2mV+XepuxnOtihiYgL/XuqwUYU2QI7jYfF/MppVAWE=; b=kMLYZM8568BAtltBQmGHrhMwUog80Ausj2WcGhUCsWMqy4V96L40y64WFopA4Fetc8 g7/u/edIxv3JMCcnA2qlRBAuyD91uKr0k5vmpgLU1uTcm1jKMDFpFaGo+RDBLF/7iSO0 6E8o2I9XUpi/hL7giCPkBRs/UcI/71FLBOzDKmN5KAUMogutltaC1ZnK53tNIH2fD0fp Z1KgrTsInRD1R56IfN3vdqNbHkQKE497lKEptWA7088iw8ubGIxjUG+2w9JQz76lvRKu cApr8ZzDJb1u1ovT7kCXmE5mNkd+U5FN6ZPBj87uMXWl0Kr5zF2WqmtAuVjiYuk9l2XW ffGQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=K3ELKy0L; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h11si2504287ede.45.2019.11.13.12.31.30; Wed, 13 Nov 2019 12:31:56 -0800 (PST) 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=pass header.i=@nvidia.com header.s=n1 header.b=K3ELKy0L; 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=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726969AbfKMUay (ORCPT + 99 others); Wed, 13 Nov 2019 15:30:54 -0500 Received: from hqemgate14.nvidia.com ([216.228.121.143]:5469 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726270AbfKMUax (ORCPT ); Wed, 13 Nov 2019 15:30:53 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Wed, 13 Nov 2019 12:30:51 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Wed, 13 Nov 2019 12:30:48 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Wed, 13 Nov 2019 12:30:48 -0800 Received: from [10.2.160.107] (172.20.13.39) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 13 Nov 2019 20:30:47 +0000 Subject: Re: [PATCH v3 00/23] mm/gup: track dma-pinned pages: FOLL_PIN, FOLL_LONGTERM To: Jan Kara , Jason Gunthorpe , Andrew Morton , Al Viro , Alex Williamson , Benjamin Herrenschmidt , =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= , Christoph Hellwig , Dan Williams , Dave Chinner , David Airlie , "David S . Miller" , Ira Weiny , Jens Axboe , Jonathan Corbet , =?UTF-8?B?SsOpcsO0bWUgR2xpc3Nl?= , Magnus Karlsson , Mauro Carvalho Chehab , Michael Ellerman , Michal Hocko , Mike Kravetz , Paul Mackerras , Shuah Khan , Vlastimil Babka , bpf , dri-devel , , , Linux Doc Mailing List , , "open list:KERNEL SELFTEST FRAMEWORK" , "open list:DMA BUFFER SHARING FRAMEWORK" , , linuxppc-dev , netdev , Linux MM , LKML References: <20191112000700.3455038-1-jhubbard@nvidia.com> <20191112203802.GD5584@ziepe.ca> <02fa935c-3469-b766-b691-5660084b60b9@nvidia.com> <7b671bf9-4d94-f2cc-8453-863acd5a1115@nvidia.com> <20191113101210.GD6367@quack2.suse.cz> <20191113114311.GP23790@phenom.ffwll.local> From: John Hubbard X-Nvconfidentiality: public Message-ID: <283b121d-f526-f43f-de45-dc2f8318d860@nvidia.com> Date: Wed, 13 Nov 2019 12:28:02 -0800 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: <20191113114311.GP23790@phenom.ffwll.local> X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1573677051; bh=w2mV+XepuxnOtihiYgL/XuqwUYU2QI7jYfF/MppVAWE=; h=X-PGP-Universal:Subject:To:References:From:X-Nvconfidentiality: Message-ID:Date:User-Agent:MIME-Version:In-Reply-To: X-Originating-IP:X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=K3ELKy0LEaE4Frm6QQ4jLw8cJF3zobatTYiyQ/Vg2jO630IkqTksnY4sEeXMrgt5a b46qAh7TsgPVJKCPcTPIoUnjxNn6h2xUdpivOkXuz3queuSeoxqaSFBxc3yHdAdKf1 weqLMTvKu8Vs4tf6la1SbXQc5ZvBvuc6pK240FvHmEYJ0o2WePNqZANag+FSCa5U1i 2iyzSKadjF0T/uRVrR4KM4Ey20Bg7sJaaQBcaSS9Pr1q7odGMaBmeJ4hRBriIHKA4P 1LTpfohPn7iHAuSCtXbApQkiiVLKyUBXMKbsJDCLOd3JNZEji1iUk1dM5atghZtAzC EJVJspvV4f3sw== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/13/19 3:43 AM, Daniel Vetter wrote: ... >>>> Can't we call this unpin_user_page then, for some symmetry? Or is that >>>> even more churn? >>>> >>>> Looking from afar the naming here seems really confusing. >>> >>> >>> That look from afar is valuable, because I'm too close to the problem to see >>> how the naming looks. :) >>> >>> unpin_user_page() sounds symmetrical. It's true that it would cause more >>> churn (which is why I started off with a proposal that avoids changing the >>> names of put_user_page*() APIs). But OTOH, the amount of churn is proportional >>> to the change in direction here, and it's really only 10 or 20 lines changed, >>> in the end. >>> >>> So I'm open to changing to that naming. It would be nice to hear what others >>> prefer, too... >> >> FWIW I'd find unpin_user_page() also better than put_user_page() as a >> counterpart to pin_user_pages(). > > One more point from afar on pin/unpin: We use that a lot in graphics for > permanently pinned graphics buffer objects. Which really only should be > used for scanout. So at least graphics folks should have an appropriate > mindset and try to make sure we don't overuse this stuff. > -Daniel > OK, Ira also likes "unpin", and so far no one has said *anything* in favor of the "put_user_page" names, so I think we have a winner! I'll change the names to unpin_user_page*(). thanks, -- John Hubbard NVIDIA