From: Jeff Moyer Subject: Re: [PATCH 2/2] dax: move writeback calls into the filesystems Date: Mon, 08 Feb 2016 15:58:44 -0500 Message-ID: References: <1454829553-29499-1-git-send-email-ross.zwisler@linux.intel.com> <1454829553-29499-3-git-send-email-ross.zwisler@linux.intel.com> <20160207215047.GJ31407@dastard> <20160208201808.GK27429@dastard> Mime-Version: 1.0 Content-Type: text/plain Cc: Dave Chinner , Ross Zwisler , "linux-kernel\@vger.kernel.org" , "Theodore Ts'o" , Alexander Viro , Andreas Dilger , Andrew Morton , Jan Kara , Matthew Wilcox , linux-ext4 , linux-fsdevel , Linux MM , "linux-nvdimm\@lists.01.org" , XFS Developers To: Dan Williams Return-path: In-Reply-To: (Dan Williams's message of "Mon, 8 Feb 2016 12:55:24 -0800") Sender: owner-linux-mm@kvack.org List-Id: linux-ext4.vger.kernel.org Dan Williams writes: > I agree the mount option needs to die, and I fully grok the reasoning. > What I'm concerned with is that a system using fully-DAX-aware > applications is forced to incur the overhead of maintaining *sync > semantics, periodic sync(2) in particular, even if it is not relying > on those semantics. > > However, like I said in my other mail, we can solve that with > alternate interfaces to persistent memory if that becomes an issue and > not require that "disable *sync" capability to come through DAX. What do you envision these alternate interfaces looking like? -Jeff -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org