From: Dan Williams <dan.j.williams@intel.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/3] xfs: remove dax EXPERIMENTAL warning
Date: Wed, 15 Sep 2021 11:54:01 -0700 [thread overview]
Message-ID: <CAPcyv4jyo-z7Ndx2hD9hYtTP7Q4ccrEnc2vEqdhq-dct1D0_-Q@mail.gmail.com> (raw)
In-Reply-To: <1631726561-16358-2-git-send-email-sandeen@redhat.com>
On Wed, Sep 15, 2021 at 10:23 AM Eric Sandeen <sandeen@redhat.com> wrote:
>
> As there seems to be no significant outstanding concern about
> dax on xfs at this point, remove the scary EXPERIMENTAL
> warning when in use.
>
> (dax+reflink is still unimplemented, but that can be considered
> a future feature, and doesn't require a warning for the
> non-reflink usecase.)
The original concern was that dax-reflink could not be implemented
without ABI regressions. As far as I can see that concern has been put
to rest by the proposed patches. Am I wrong? So, if we're committed to
not breaking past promises I think this change can be made
out-of-order from when the reflink support patches land.
Acked-by: Dan Williams <dan.j.williams@intel.com>
...but I'm also fine with waiting for the final reflink merge.
next prev parent reply other threads:[~2021-09-15 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 17:22 [PATCH 0/3 RFC] Remove DAX experimental warnings Eric Sandeen
2021-09-15 17:22 ` [PATCH 1/3] xfs: remove dax EXPERIMENTAL warning Eric Sandeen
2021-09-15 18:54 ` Dan Williams [this message]
2021-09-15 17:22 ` [PATCH 2/3] ext4: " Eric Sandeen
2021-09-17 9:47 ` Jan Kara
2021-09-15 17:22 ` [PATCH 3/3] ext2: " Eric Sandeen
2021-09-17 9:47 ` Jan Kara
2021-09-17 12:59 ` Christoph Hellwig
2021-09-17 14:09 ` Eric Sandeen
2021-09-22 2:36 ` Darrick J. Wong
2021-09-22 5:25 ` Christoph Hellwig
2021-09-15 18:35 ` [PATCH 0/3 RFC] Remove DAX experimental warnings Dan Williams
2021-09-15 18:48 ` Eric Sandeen
2021-09-15 18:59 ` Dan Williams
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=CAPcyv4jyo-z7Ndx2hD9hYtTP7Q4ccrEnc2vEqdhq-dct1D0_-Q@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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).