From: Christoph Hellwig <hch@lst.de>
To: Brian Foster <bfoster@redhat.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: remove experimental tag for reflinks
Date: Thu, 31 Aug 2017 15:30:19 +0200 [thread overview]
Message-ID: <20170831133019.GA5468@lst.de> (raw)
In-Reply-To: <20170831124321.GA21939@bfoster.bfoster>
On Thu, Aug 31, 2017 at 08:43:21AM -0400, Brian Foster wrote:
> FWIW, I don't really have a strong opinion. To me, removing experimental
> means we feel the code has stabilized long enough in principle, there
> are no significant problems (i.e., corruption/crash vectors) that we are
> aware of and the feature is complete (full userspace tool support, etc).
> The in-core extent list thing seems like more of a general problem to me
Agreed so far.
> That aside, shouldn't we consider the rmapbt experimental tag first, or
> at least at the same time? It's been around for slightly longer.
I've not done much testing on that or have experience with it in general,
nor do I have a customer with a big QA team beating it hard, so I can't
really comment on that one.
next prev parent reply other threads:[~2017-08-31 13:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 14:54 [PATCH] xfs: remove experimental tag for reflinks Christoph Hellwig
2017-08-31 6:40 ` Darrick J. Wong
2017-08-31 12:43 ` Brian Foster
2017-08-31 13:30 ` Christoph Hellwig [this message]
2017-08-31 15:31 ` Darrick J. Wong
2017-08-31 15:55 ` Eric Sandeen
2017-08-31 20:02 ` Darrick J. Wong
2017-08-31 15:59 ` Brian Foster
2017-08-31 20:09 ` Darrick J. Wong
2017-08-31 20:36 ` Brian Foster
2017-08-31 22:58 ` Dave Chinner
2017-09-01 11:16 ` Brian Foster
2017-08-31 22:19 ` Dave Chinner
2018-01-08 21:43 ` Darrick J. Wong
2018-01-08 22:11 ` Dave Chinner
2017-11-15 1:10 ` Darrick J. Wong
2017-11-15 6:14 ` Amir Goldstein
2017-11-22 18:31 ` Darrick J. Wong
2017-11-22 20:40 ` Amir Goldstein
2017-11-22 21:00 ` Darrick J. Wong
2017-11-23 10:44 ` Amir Goldstein
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=20170831133019.GA5468@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.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 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).