From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: mtk.manpages@gmail.com, darrick.wong@oracle.com
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
hch@infradead.org, linux-man@vger.kernel.org
Subject: [PATCH v5 0/2] man-pages: document reflink/dedupe ioctls
Date: Tue, 15 Mar 2016 09:48:04 -0700 [thread overview]
Message-ID: <20160315164804.30909.83270.stgit@birch.djwong.org> (raw)
Hi all,
This patch set goes along with the fifth revision of an RFC adding to
XFS kernel support for tracking reverse-mappings of physical blocks to
file and metadata; and support for mapping multiple file logical
blocks to the same physical block, more commonly known as reflinking.
The two patches in this series document the clone, clone_range, and
dedupe ioctls in the form of man pages.
The patch set is based on a whole pile of proposed patches against the
current (4.5) upstream kernel; the ioctls are simply hoisted version
of the private btrfs ioctls.
Comments and questions are, as always, welcome.
--D
next reply other threads:[~2016-03-15 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 16:48 Darrick J. Wong [this message]
2016-03-15 16:48 ` [PATCH 1/2] man2: document FICLONE and FICLONERANGE Darrick J. Wong
2016-03-19 17:04 ` walter harms
2016-03-20 19:13 ` Darrick J. Wong
2016-06-08 10:35 ` Michael Kerrisk (man-pages)
2016-03-15 16:48 ` [PATCH 2/2] man2: document the FIDEDUPERANGE ioctl Darrick J. Wong
2016-06-08 10:35 ` Michael Kerrisk (man-pages)
2016-06-08 16:39 ` Darrick J. Wong
2016-03-15 17:04 ` [PATCH v5 0/2] man-pages: document reflink/dedupe ioctls Christoph Hellwig
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=20160315164804.30909.83270.stgit@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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).