From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0E449C433F5 for ; Mon, 13 Dec 2021 08:24:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232953AbhLMIYc (ORCPT ); Mon, 13 Dec 2021 03:24:32 -0500 Received: from verein.lst.de ([213.95.11.211]:46663 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233027AbhLMIYX (ORCPT ); Mon, 13 Dec 2021 03:24:23 -0500 Received: by verein.lst.de (Postfix, from userid 2407) id 60ABF68BFE; Mon, 13 Dec 2021 09:24:20 +0100 (CET) Date: Mon, 13 Dec 2021 09:24:20 +0100 From: Christoph Hellwig To: Dan Williams Cc: Christoph Hellwig , Vishal Verma , Dave Jiang , Alasdair Kergon , Mike Snitzer , Ira Weiny , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Vivek Goyal , Stefan Hajnoczi , Miklos Szeredi , Matthew Wilcox , device-mapper development , Linux NVDIMM , linux-s390 , linux-fsdevel , virtualization@lists.linux-foundation.org Subject: Re: [PATCH 4/5] dax: remove the copy_from_iter and copy_to_iter methods Message-ID: <20211213082420.GC21462@lst.de> References: <20211209063828.18944-1-hch@lst.de> <20211209063828.18944-5-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Sun, Dec 12, 2021 at 06:39:16AM -0800, Dan Williams wrote: > > /* flag to check if device supports synchronous flush */ > > DAXDEV_SYNC, > > + /* do not use uncached operations to write data */ > > + DAXDEV_CACHED, > > + /* do not use mcsafe operations to read data */ > > + DAXDEV_NOMCSAFE, > > Linus did not like the mcsafe name, and this brings it back. Let's > flip the polarity to positively indicate which routine to use, and to > match the 'nofault' style which says "copy and handle faults". > > /* do not leave the caches dirty after writes */ > DAXDEV_NOCACHE > > /* handle CPU fetch exceptions during reads */ > DAXDEV_NOMC > > ...and then flip the use cases around. Sure we can do that. But let's finish the discussion if we actually need the virtiofs special casing, as it seems pretty fishy in many aspects.