All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: "Darrick J. Wong" <darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org,
	linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [LSF/MM TOPIC] Future direction of DAX
Date: Mon, 16 Jan 2017 23:57:35 -0800	[thread overview]
Message-ID: <20170117075735.GB19654@infradead.org> (raw)
In-Reply-To: <20170117015033.GD10498-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>

On Mon, Jan 16, 2017 at 05:50:33PM -0800, Darrick J. Wong wrote:
> I wouldn't consider it a barrier in general (since ext4 also prints
> EXPERIMENTAL warnings for DAX), merely one for XFS.  I don't even think
> it's that big of a hurdle -- afaict XFS ought to be able to achieve this
> by modifying iomap_begin to allocate new pmem blocks, memcpy the
> contents, and update the memory mappings.  I think.

Yes, and I have a working prototype for that.  I'm just way to busy
with lots of bugfixing at the moment but I plan to get to it in this
merge window.  I also agree that we can't mark a feature as fully
supported until it doesn't conflict with other features.

And I'm not going to get start on the PMEM_IMMUTABLE bullshit, please
don't even go there folks, it's a dead end.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-nvdimm@ml01.01.org, linux-block@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] Future direction of DAX
Date: Mon, 16 Jan 2017 23:57:35 -0800	[thread overview]
Message-ID: <20170117075735.GB19654@infradead.org> (raw)
In-Reply-To: <20170117015033.GD10498@birch.djwong.org>

On Mon, Jan 16, 2017 at 05:50:33PM -0800, Darrick J. Wong wrote:
> I wouldn't consider it a barrier in general (since ext4 also prints
> EXPERIMENTAL warnings for DAX), merely one for XFS.  I don't even think
> it's that big of a hurdle -- afaict XFS ought to be able to achieve this
> by modifying iomap_begin to allocate new pmem blocks, memcpy the
> contents, and update the memory mappings.  I think.

Yes, and I have a working prototype for that.  I'm just way to busy
with lots of bugfixing at the moment but I plan to get to it in this
merge window.  I also agree that we can't mark a feature as fully
supported until it doesn't conflict with other features.

And I'm not going to get start on the PMEM_IMMUTABLE bullshit, please
don't even go there folks, it's a dead end.


WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-nvdimm@ml01.01.org, linux-block@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] Future direction of DAX
Date: Mon, 16 Jan 2017 23:57:35 -0800	[thread overview]
Message-ID: <20170117075735.GB19654@infradead.org> (raw)
In-Reply-To: <20170117015033.GD10498@birch.djwong.org>

On Mon, Jan 16, 2017 at 05:50:33PM -0800, Darrick J. Wong wrote:
> I wouldn't consider it a barrier in general (since ext4 also prints
> EXPERIMENTAL warnings for DAX), merely one for XFS.  I don't even think
> it's that big of a hurdle -- afaict XFS ought to be able to achieve this
> by modifying iomap_begin to allocate new pmem blocks, memcpy the
> contents, and update the memory mappings.  I think.

Yes, and I have a working prototype for that.  I'm just way to busy
with lots of bugfixing at the moment but I plan to get to it in this
merge window.  I also agree that we can't mark a feature as fully
supported until it doesn't conflict with other features.

And I'm not going to get start on the PMEM_IMMUTABLE bullshit, please
don't even go there folks, it's a dead end.

--
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>

  parent reply	other threads:[~2017-01-17  7:57 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14  0:20 [LSF/MM TOPIC] Future direction of DAX Ross Zwisler
2017-01-14  0:20 ` Ross Zwisler
2017-01-14  0:20 ` Ross Zwisler
     [not found] ` <20170114002008.GA25379-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-01-14  8:26   ` Darrick J. Wong
2017-01-14  8:26     ` Darrick J. Wong
2017-01-14  8:26     ` Darrick J. Wong
2017-01-16  0:19     ` Viacheslav Dubeyko
2017-01-16  0:19       ` Viacheslav Dubeyko
2017-01-16  0:19       ` Viacheslav Dubeyko
2017-01-16 20:00     ` Jeff Moyer
2017-01-16 20:00       ` Jeff Moyer
2017-01-17  1:50       ` Darrick J. Wong
2017-01-17  1:50         ` Darrick J. Wong
2017-01-17  2:42         ` Dan Williams
2017-01-17  2:42           ` Dan Williams
     [not found]         ` <20170117015033.GD10498-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2017-01-17  7:57           ` Christoph Hellwig [this message]
2017-01-17  7:57             ` Christoph Hellwig
2017-01-17  7:57             ` Christoph Hellwig
2017-01-17 14:54             ` Jeff Moyer
2017-01-17 14:54               ` Jeff Moyer
     [not found]               ` <x49mvep4tzw.fsf-RRHT56Q3PSP4kTEheFKJxxDDeQx5vsVwAInAS/Ez/D0@public.gmane.org>
2017-01-17 15:06                 ` Christoph Hellwig
2017-01-17 15:06                   ` Christoph Hellwig
2017-01-17 15:06                   ` Christoph Hellwig
     [not found]                   ` <20170117150638.GA3747-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-01-17 16:07                     ` Jeff Moyer
2017-01-17 16:07                       ` Jeff Moyer
2017-01-17 16:07                       ` Jeff Moyer
2017-01-17 15:59 ` [Lsf-pc] " Jan Kara
2017-01-17 15:59   ` Jan Kara
2017-01-17 15:59   ` Jan Kara
2017-01-17 16:56   ` Dan Williams
2017-01-17 16:56     ` Dan Williams
2017-01-17 16:56     ` Dan Williams
2017-01-18  0:03   ` Kani, Toshimitsu
2017-01-18  0:03     ` Kani, Toshimitsu
2017-01-18  0:03     ` Kani, Toshimitsu
2017-01-18  5:25 ` willy
2017-01-18  5:25   ` willy
2017-01-18  5:25   ` willy
2017-01-18  6:01   ` Dan Williams
2017-01-18  6:01     ` Dan Williams
2017-01-18  6:01     ` Dan Williams
2017-01-18  6:07     ` willy
2017-01-18  6:07       ` willy
2017-01-18  6:07       ` willy
2017-01-18  6:25       ` Dan Williams
2017-01-18  6:25         ` Dan Williams
2017-01-18  6:25         ` Dan Williams
2017-01-18 17:22   ` Ross Zwisler
2017-01-18 17:22     ` Ross Zwisler
2017-01-18 17:22     ` 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=20170117075735.GB19654@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org \
    --cc=lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /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.