[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151224101111.GA6438@infradead.org>
Date: Thu, 24 Dec 2015 02:11:11 -0800
From: Christoph Hellwig <hch@...radead.org>
To: "Elliott, Robert (Persistent Memory)" <elliott@....com>
Cc: Cholerae Hu <choleraehyq@...il.com>,
Dan Williams <dan.j.williams@...el.com>,
Dave Chinner <david@...morbit.com>, Ted Tso <tytso@....edu>,
"adilger.kernel@...ger.ca" <adilger.kernel@...ger.ca>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...1.01.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"xfs@....sgi.com" <xfs@....sgi.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: A blocksize problem about dax and ext4
On Thu, Dec 24, 2015 at 02:47:07AM +0000, Elliott, Robert (Persistent Memory) wrote:
> > 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.
No, it doesn't. File you use for DAX must be aligne at page size
granularity. For XFS you could do this with the per-inode extent size
hint for example even if the overall block size is smaller.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists