From: Chris Mason <clm@fb.com>
To: Matthew Wilcox <willy@linux.intel.com>,
Purush Gupta <purush.gupta@nutanix.com>
Cc: "Martin K. Petersen" <mkp@mkp.net>,
"Theodore Ts'o" <tytso@mit.edu>,
Dave Chinner <david@fromorbit.com>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: Write atomicity guarantees
Date: Thu, 24 Apr 2014 14:44:21 -0400 [thread overview]
Message-ID: <53595B85.4090703@fb.com> (raw)
In-Reply-To: <20140424182513.GD5886@linux.intel.com>
On 04/24/2014 02:25 PM, Matthew Wilcox wrote:
> 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.
>
That's my feeling. The non-vectored use case is pretty limited, mostly
to help get a contiguous log entry on disk as a full unit. But most of
the time the filesystem log commits are pretty big. Workloads with a
very small number of latency sensitive writers would see improvements.
We could also the contiguous atomics for something like mysql by using a
16K sector size in the filesystem. At that point all of the db 16K
units will be contig and the existing atomics proposals become interesting.
But I was really hoping for the vectors ;)
-chris
prev parent reply other threads:[~2014-04-24 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 17:39 Write atomicity guarantees Matthew Wilcox
2014-04-24 18:03 ` Chris Mason
2014-04-24 18:23 ` Dan Williams
2014-04-24 18:50 ` Chris Mason
2014-04-24 19:27 ` Dave Chinner
[not found] ` <CAN7X1U=yjcxW16C8H9G5WWEOj1S5Wh0O26WpE5QrC38biRShtw@mail.gmail.com>
2014-04-24 18:25 ` Matthew Wilcox
2014-04-24 18:44 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53595B85.4090703@fb.com \
--to=clm@fb.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mkp@mkp.net \
--cc=purush.gupta@nutanix.com \
--cc=tytso@mit.edu \
--cc=willy@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).