From: "Elliott, Robert (Persistent Memory)" Subject: RE: A blocksize problem about dax and ext4 Date: Thu, 24 Dec 2015 02:47:07 +0000 Message-ID: <94D0CD8314A33A4D9D801C0FE68B40295BEC9CDD@G9W0745.americas.hpqcorp.net> References: <94D0CD8314A33A4D9D801C0FE68B40295BEC985F@G9W0745.americas.hpqcorp.net> <20151224000021.GU19802@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Ted Tso , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" , "xfs@oss.sgi.com" , "adilger.kernel@dilger.ca" , "linux-ext4@vger.kernel.org" To: Cholerae Hu , Dan Williams Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-ext4.vger.kernel.org > -----Original Message----- > From: Cholerae Hu [mailto:choleraehyq@gmail.com] > Sent: Wednesday, December 23, 2015 8:36 PM > Subject: Re: A blocksize problem about dax and ext4 ... > xfs will silently disable dax when the fs block size is too small, > i.e. your mmap() operations are backed by page cache in this case. > Currently the only indication of whether a mapping is DAX backed or > not is the presence of the VM_MIXEDMAP flag ("mm" in the VmFlags field > of /proc//smaps) > > Did you mean that I should make the blocksize bigger until the mount > command tell me that dax is enabled? To really use DAX, the filesystem block size must match the system CPU's page size, which is probably 4096 bytes. --- Robert Elliott, HPE Persistent Memory _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs