linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Brian Foster <bfoster@redhat.com>,
	linux-xfs@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>,
	Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH] xfs: remove experimental tag for reflinks
Date: Thu, 31 Aug 2017 08:31:48 -0700	[thread overview]
Message-ID: <20170831153148.GJ3775@magnolia> (raw)
In-Reply-To: <20170831133019.GA5468@lst.de>

On Thu, Aug 31, 2017 at 03:30:19PM +0200, Christoph Hellwig wrote:
> 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.

<nod> Dave?  Eric?  Any perspective you'd like to offer? :)

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

rmapbt will remain EXPERIMENTAL because I still have more patches to
send to finish the feature for realtime devices.  Speaking of which,
it's now been 53 weeks since the last dump of that, so I'll go do that
now. :P

FWIW I /also/ run rmapbt everywhere and haven't had any trouble with it
since adding the per-AG reservations.

--D

> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-31 15:31 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
2017-08-31 15:31       ` Darrick J. Wong [this message]
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=20170831153148.GJ3775@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --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).