public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: david@fromorbit.com, hch@infradead.org
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>, xfs <xfs@oss.sgi.com>
Subject: RFCv3+ WIP rollup of XFS reverse-mapping, reflink, and dedupe support
Date: Wed, 11 Nov 2015 10:55:10 -0800	[thread overview]
Message-ID: <20151111185510.GC2224@birch.djwong.org> (raw)

Hi all,

Today I've uploaded the latest WIP patches for XFS reverse mapping,
reflink, and dedupe support to github:

https://github.com/djwong/linux/tree/for-dave
https://github.com/djwong/xfsprogs/tree/for-dave
https://github.com/djwong/xfstests/tree/for-dave
https://github.com/djwong/xfs-documentation/tree/for-dave

I've cleaned things up so now you can pull the for-dave branch in any
of the four repositories.

I updated the XFS on-disk format documentation to fix numerous
omissions in the second edition and to reflect v5 XFS and the
rmap/reflink additions to the filesystem.

Since RFCv3, I restructured how bmbt updates get reflected in the
rmapbt -- now they're deferred until xfs_bmap_finish time, so that the
rmap btree updates obey AG locking order rules to avoid deadlocks.
I also fixed numerous minor bookkeeping bugs in the rmapbt and
refcountbt code.  Lastly, I pulled in Anna Schumaker and Peng Tao's
patches hoisting the reflink ioctls into the VFS, added patches to do
the same with the dedupe ioctl, and wired up XFS to both of the new
VFS operations.

The tests have been reworked (I hope) to play more nicely with NFS
reflink -- now we simply test the xfs_io reflink or dedupe commands on
the test or scratch FS to decide if we're going to run the test,
instead of inferring it from FS type.  The fiemap checks are gone,
replaced with umount, mount, and verifying file contents. 

xfsprogs hasn't changed much, other than porting kernel-side changes.

I will post the xfstests and xfs-documentation patches on the list
shortly.

I'm holding off on reposting the kernel and xfsprogs patches because
I'm still working on fixing CoW and don't really want to blast the
mailing lists again until I'm done with that.

--D

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

                 reply	other threads:[~2015-11-11 18:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151111185510.GC2224@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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