From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:60638 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338AbdAVSat (ORCPT ); Sun, 22 Jan 2017 13:30:49 -0500 Date: Sun, 22 Jan 2017 19:30:46 +0100 From: Christoph Hellwig To: Matthew Wilcox Cc: Christoph Hellwig , Dan Williams , "linux-nvdimm@lists.01.org" , Brian Boylston , Tony Luck , Jan Kara , Toshi Kani , Mike Snitzer , "linux-kernel@vger.kernel.org" , "x86@kernel.org" , Jeff Moyer , Jens Axboe , "dm-devel@redhat.com" , Ingo Molnar , Al Viro , "H. Peter Anvin" , "linux-fsdevel@vger.kernel.org" , Thomas Gleixner , Linus Torvalds , Ross Zwisler Subject: Re: [PATCH 00/13] dax, pmem: move cpu cache maintenance to libnvdimm Message-ID: <20170122183046.GA7359@lst.de> References: <148488421301.37913.12835362165895864897.stgit@dwillia2-desk3.amr.corp.intel.com> <20170121175212.GA28180@lst.de> <20170122162910.GA5267@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Jan 22, 2017 at 06:19:24PM +0000, Matthew Wilcox wrote: > No, I mean a network filesystem like 9p or cifs or nfs. If the memcpy > is supposed to be performed by the backing device struct backing_dev has no relation to the DAX code. Even more so what's the point of doing a DAXish memcpy in that case? If we buffer in memory for network I/O we should just use the page cache. > (Also, the network filesystem might have a command, like RDMA has/will have, to ensure that the write has reached persistence) I know very well due to my work for a DAX-backed pNFS layout. But that is mostly transparent to the NFS frontend code and won't use DAX on the client at all. Just pagecache as a source for RDMA READ/WRITE.