From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Write atomicity guarantees Date: Thu, 24 Apr 2014 14:25:13 -0400 Message-ID: <20140424182513.GD5886@linux.intel.com> References: <20140424173909.GB5886@linux.intel.com> <53595209.50906@fb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Mason , "Martin K. Petersen" , Theodore Ts'o , Dave Chinner , linux-fsdevel@vger.kernel.org To: Purush Gupta Return-path: Received: from mga01.intel.com ([192.55.52.88]:62337 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757915AbaDXSZP (ORCPT ); Thu, 24 Apr 2014 14:25:15 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Apr 24, 2014 at 11:10:09AM -0700, Purush Gupta wrote: > That would require a new NVMe write command semantic with descriptors > currently its not there. Yes ... I don't want to start defining such a command on linux-fsdevel. What I'm hearing is that there's no benefit to a device that can guarantee to write multiple contiguous sectors in a non-torn manner over a device that can write a single sector in a non-torn manner. For any real benefit, filesystems need (and Linux needs to introduce plumbing for) vectored atomic writes.