From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751774AbdAVSos (ORCPT ); Sun, 22 Jan 2017 13:44:48 -0500 Received: from verein.lst.de ([213.95.11.211]:60784 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750999AbdAVSok (ORCPT ); Sun, 22 Jan 2017 13:44:40 -0500 Date: Sun, 22 Jan 2017 19:44:39 +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: <20170122184439.GA7603@lst.de> References: <148488421301.37913.12835362165895864897.stgit@dwillia2-desk3.amr.corp.intel.com> <20170121175212.GA28180@lst.de> <20170122162910.GA5267@lst.de> <20170122183046.GA7359@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) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 22, 2017 at 06:39:28PM +0000, Matthew Wilcox wrote: > Two guests on the same physical machine (or a guest and a host) have access to the same set of physical addresses. This might be an NV-DIMM, or it might just be DRAM (for the purposes of reducing guest overhead). The network filesystem has been enhanced with a call to allow the client to ask the server "What is the physical address for this range of bytes in this file?" > > We don't want to use the guest pagecache here. That's antithetical to the second usage, and it's inefficient for the first usage. And the answer is that you need a dax device for whatever memoery exposed in this way, as it needs to show up in the memory map for example.