Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1037747pxj; Thu, 17 Jun 2021 20:53:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw1Chd+RaYc9IOuNh5BnhmErWQZvxHaucuV0ODULIuFt2KQTGtHbNIMthFwViePt/3QV2r3 X-Received: by 2002:aa7:c6d4:: with SMTP id b20mr2097194eds.341.1623988404050; Thu, 17 Jun 2021 20:53:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623988404; cv=none; d=google.com; s=arc-20160816; b=Zqukk4BMmqvX2hrcBPl93fZELYiyTe8oZdx8QlTPT1/24C/PwDeFy1Z863uRslSaLc QrS77fO12iNRxAHsAMixUIGK+tS6o5R3TPliPqNLvzcJ+m1h8OB9ZXnFyu9JZxJjQnXP v0ecZYYe7XKbj5yGB+E/ejKNhHvNjlMlaajZq88V/2UL/z0yknj08m2ofzPVnyuXcrEN BICVMD/GJCvRyQwhSxT30NStL1SaKc+/H1OZcFckcuaxEf/iX+SVYp4hK7K7Wp9qj38D 03liyXLt3bii/HRBEvGkn0GiyJZKfEtU7xxB1P8PGR/AL7XygOzAJtmMuAzTPTsMJWvs lBwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=TS5ssGSubRTyBqEK1nZKaUE6iOjlw+//IJ2IyhE3wBg=; b=XtoIC4yzXhP6bZUt/1/iVIthZ/Iy61ditOqDwg/DdedP71yP6psZOAnL8DrhICRgFS 0CaoHmOcYfQntziMKyP1sBXDAbUYMKWDw6uNoQ1RwLTbSKidjQzXMUpIvcqo9XwZUjKX tQSBOnO8QG/WslWX4AvkH6dLwvXhpjqq15ar/CUcUkRj+nal6zUH4JH3f5fcFN0QqlC9 PeMSF6ZHOmncy/fma/Cu/EVqWw/FSyicZ2Ab5Xk1CNwd12Oe1nH9BgoAoa6Obg6desN8 Kqhpdw1CSVK9QoQEjRYE2abUobKuRNBnITeG4HpWEQER0JNMakbVcJR7pgBuCNHPtjJs y2Vg== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 16si1083846ejd.349.2021.06.17.20.53.01; Thu, 17 Jun 2021 20:53:24 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231908AbhFRDkj (ORCPT + 99 others); Thu, 17 Jun 2021 23:40:39 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:50748 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229819AbhFRDki (ORCPT ); Thu, 17 Jun 2021 23:40:38 -0400 Received: from gondobar.mordor.me.apana.org.au ([192.168.128.4] helo=gondobar) by deadmen.hmeau.com with esmtp (Exim 4.92 #5 (Debian)) id 1lu5KJ-0000aH-Fe; Fri, 18 Jun 2021 11:37:51 +0800 Received: from herbert by gondobar with local (Exim 4.92) (envelope-from ) id 1lu5Jw-0004Nh-Un; Fri, 18 Jun 2021 11:37:28 +0800 Date: Fri, 18 Jun 2021 11:37:28 +0800 From: Herbert Xu To: Ira Weiny Cc: Christoph Hellwig , Jens Axboe , Thomas Gleixner , Thomas Bogendoerfer , Geoff Levand , Ilya Dryomov , Dongsheng Yang , Mike Snitzer , "James E.J. Bottomley" , dm-devel@redhat.com, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, ceph-devel@vger.kernel.org, linux-arch@vger.kernel.org, "David S. Miller" , Christoph Lameter Subject: Re: [PATCH 01/18] mm: add a kunmap_local_dirty helper Message-ID: <20210618033728.GA16787@gondor.apana.org.au> References: <20210615132456.753241-1-hch@lst.de> <20210615132456.753241-2-hch@lst.de> <20210618030157.GA1905674@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210618030157.GA1905674@iweiny-DESK2.sc.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 17, 2021 at 08:01:57PM -0700, Ira Weiny wrote: > > > + flush_kernel_dcache_page(__page); \ > > Is this required on 32bit systems? Why is kunmap_flush_on_unmap() not > sufficient on 64bit systems? The normal kunmap_local() path does that. > > I'm sorry but I did not see a conclusion to my query on V1. Herbert implied the > he just copied from the crypto code.[1] I'm concerned that this _dirty() call > is just going to confuse the users of kmap even more. So why can't we get to > the bottom of why flush_kernel_dcache_page() needs so much logic around it > before complicating the general kernel users. > > I would like to see it go away if possible. This thread may be related: https://lwn.net/Articles/240249/ Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt