From: Dan Williams <dan.j.williams@intel.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.com>, Matthew Wilcox <willy@linux.intel.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
XFS Developers <xfs@oss.sgi.com>
Subject: Re: [PATCH 2/2] dax: move writeback calls into the filesystems
Date: Mon, 8 Feb 2016 14:05:34 -0800 [thread overview]
Message-ID: <CAPcyv4iHaFNBRBb4EYPfHX+pB5srJbqrOX7FnDXyDPy92Cnpww@mail.gmail.com> (raw)
In-Reply-To: <x49vb5yvrzv.fsf@segfault.boston.devel.redhat.com>
On Mon, Feb 8, 2016 at 12:58 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
> Dan Williams <dan.j.williams@intel.com> 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?
Well, plan-A was making DAX be explicit opt-in for applications, I
haven't thought too much about plan-B. I expect it to be driven by
real performance numbers and application use cases once the *sync
compat work completes.
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.com>, Matthew Wilcox <willy@linux.intel.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
XFS Developers <xfs@oss.sgi.com>
Subject: Re: [PATCH 2/2] dax: move writeback calls into the filesystems
Date: Mon, 8 Feb 2016 14:05:34 -0800 [thread overview]
Message-ID: <CAPcyv4iHaFNBRBb4EYPfHX+pB5srJbqrOX7FnDXyDPy92Cnpww@mail.gmail.com> (raw)
In-Reply-To: <x49vb5yvrzv.fsf@segfault.boston.devel.redhat.com>
On Mon, Feb 8, 2016 at 12:58 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
> Dan Williams <dan.j.williams@intel.com> 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?
Well, plan-A was making DAX be explicit opt-in for applications, I
haven't thought too much about plan-B. I expect it to be driven by
real performance numbers and application use cases once the *sync
compat work completes.
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
XFS Developers <xfs@oss.sgi.com>, Linux MM <linux-mm@kvack.org>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Matthew Wilcox <willy@linux.intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] dax: move writeback calls into the filesystems
Date: Mon, 8 Feb 2016 14:05:34 -0800 [thread overview]
Message-ID: <CAPcyv4iHaFNBRBb4EYPfHX+pB5srJbqrOX7FnDXyDPy92Cnpww@mail.gmail.com> (raw)
In-Reply-To: <x49vb5yvrzv.fsf@segfault.boston.devel.redhat.com>
On Mon, Feb 8, 2016 at 12:58 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
> Dan Williams <dan.j.williams@intel.com> 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?
Well, plan-A was making DAX be explicit opt-in for applications, I
haven't thought too much about plan-B. I expect it to be driven by
real performance numbers and application use cases once the *sync
compat work completes.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-08 22:05 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 7:19 [PATCH 0/2] DAX bdev fixes - move flushing calls to FS Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 7:19 ` [PATCH 1/2] dax: pass bdev argument to dax_clear_blocks() Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 18:19 ` Dan Williams
2016-02-07 18:19 ` Dan Williams
2016-02-07 18:19 ` Dan Williams
2016-02-08 1:46 ` Ross Zwisler
2016-02-08 1:46 ` Ross Zwisler
2016-02-08 1:46 ` Ross Zwisler
2016-02-08 4:29 ` Ross Zwisler
2016-02-08 4:29 ` Ross Zwisler
2016-02-08 4:29 ` Ross Zwisler
2016-02-07 22:03 ` Dave Chinner
2016-02-07 22:03 ` Dave Chinner
2016-02-07 22:03 ` Dave Chinner
2016-02-08 1:44 ` Ross Zwisler
2016-02-08 1:44 ` Ross Zwisler
2016-02-08 1:44 ` Ross Zwisler
2016-02-08 5:17 ` Dave Chinner
2016-02-08 5:17 ` Dave Chinner
2016-02-08 5:17 ` Dave Chinner
2016-02-08 15:34 ` Ross Zwisler
2016-02-08 15:34 ` Ross Zwisler
2016-02-08 15:34 ` Ross Zwisler
2016-02-08 15:34 ` Ross Zwisler
2016-02-07 7:19 ` [PATCH 2/2] dax: move writeback calls into the filesystems Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 7:19 ` Ross Zwisler
2016-02-07 19:13 ` Dan Williams
2016-02-07 19:13 ` Dan Williams
2016-02-07 19:13 ` Dan Williams
2016-02-07 21:50 ` Dave Chinner
2016-02-07 21:50 ` Dave Chinner
2016-02-07 21:50 ` Dave Chinner
2016-02-08 8:18 ` Dan Williams
2016-02-08 8:18 ` Dan Williams
2016-02-08 8:18 ` Dan Williams
2016-02-08 8:18 ` Dan Williams
2016-02-08 20:18 ` Dave Chinner
2016-02-08 20:18 ` Dave Chinner
2016-02-08 20:18 ` Dave Chinner
2016-02-08 20:55 ` Dan Williams
2016-02-08 20:55 ` Dan Williams
2016-02-08 20:55 ` Dan Williams
2016-02-08 20:58 ` Jeff Moyer
2016-02-08 20:58 ` Jeff Moyer
2016-02-08 20:58 ` Jeff Moyer
2016-02-08 20:58 ` Jeff Moyer
2016-02-08 22:05 ` Dan Williams [this message]
2016-02-08 22:05 ` Dan Williams
2016-02-08 22:05 ` Dan Williams
2016-02-09 9:43 ` Jan Kara
2016-02-09 9:43 ` Jan Kara
2016-02-09 9:43 ` Jan Kara
2016-02-09 16:01 ` Jan Kara
2016-02-09 16:01 ` Jan Kara
2016-02-09 16:01 ` Jan Kara
2016-02-09 16:01 ` Jan Kara
2016-02-09 18:06 ` Ross Zwisler
2016-02-09 18:06 ` Ross Zwisler
2016-02-09 18:06 ` Ross Zwisler
2016-02-09 18:06 ` Ross Zwisler
2016-02-08 18:31 ` Ross Zwisler
2016-02-08 18:31 ` Ross Zwisler
2016-02-08 18:31 ` Ross Zwisler
2016-02-08 19:23 ` Dan Williams
2016-02-08 19:23 ` Dan Williams
2016-02-08 19:23 ` Dan Williams
2016-02-08 10:48 ` Jan Kara
2016-02-08 10:48 ` Jan Kara
2016-02-08 10:48 ` Jan Kara
2016-02-08 16:12 ` Ross Zwisler
2016-02-08 16:12 ` Ross Zwisler
2016-02-08 16:12 ` Ross Zwisler
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=CAPcyv4iHaFNBRBb4EYPfHX+pB5srJbqrOX7FnDXyDPy92Cnpww@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=jack@suse.com \
--cc=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.