public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [NOPATCH v5]: XFS reverse-mapping, reflink, and dedupe support
Date: Mon, 7 Mar 2016 23:57:01 -0800	[thread overview]
Message-ID: <20160308075701.GA24365@infradead.org> (raw)
In-Reply-To: <20160305011530.GG27973@birch.djwong.org>

On Fri, Mar 04, 2016 at 05:15:30PM -0800, Darrick J. Wong wrote:
> Soooo... stuff I'm hoping to get upstream for 4.6:
> https://github.com/djwong/linux/tree/for-dave-for-4.6
> https://github.com/djwong/xfsprogs/tree/for-dave-for-4.6
> 
> Stuff I hope to get upstream:
> https://github.com/djwong/xfs-documentation/tree/reflink-devel
> https://github.com/djwong/xfstests/tree/reflink-dev
> 
> Development branch, not for upstream:
> https://github.com/djwong/linux/tree/rmap-reflink-devel
> https://github.com/djwong/xfsprogs/tree/rmap-reflink-devel

I've been testing or-dave-for-4.6 + the increased log reservation for
rmap-reflink-devel for a couple days now and it's doing fine both on
XFS itself, as well as NFS over XFS so far.  Great work!

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-03-08  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05  1:15 [NOPATCH v5]: XFS reverse-mapping, reflink, and dedupe support Darrick J. Wong
2016-03-08  7:57 ` Christoph Hellwig [this message]
2016-04-01  0:11 ` XFS reverse-mapping, reflink, and scrub update Darrick J. Wong

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=20160308075701.GA24365@infradead.org \
    --to=hch@infradead.org \
    --cc=darrick.wong@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox