From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: mtk.manpages@gmail.com
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-man@vger.kernel.org
Subject: [PATCH] fideduperange.2: fix the discussion of maximum sizes
Date: Tue, 22 Nov 2016 20:22:22 -0800 [thread overview]
Message-ID: <20161123042222.GA30324@birch.djwong.org> (raw)
Fix the discussion of the limitations on the dest_count and src_length
parameters to the fideduperange ioctl to reflect what's actually in the
kernel.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
man2/ioctl_fideduperange.2 | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/man2/ioctl_fideduperange.2 b/man2/ioctl_fideduperange.2
index 2112d10..59f0ea9 100644
--- a/man2/ioctl_fideduperange.2
+++ b/man2/ioctl_fideduperange.2
@@ -95,7 +95,7 @@ struct file_dedupe_range_info {
.in
Each deduplication operation targets
-.IR length
+.IR src_length
bytes in file descriptor
.IR dest_fd
at offset
@@ -108,8 +108,14 @@ During the call,
must be open for reading and
.IR dest_fd
must be open for writing.
-For any call to this ioctl, there may not be more than 65,536
-requests attached; each request may not exceed 16MiB.
+The combined size of the struct
+.IR file_dedupe_range
+and the struct
+.IR file_dedupe_range_info
+array must not exceed the system page size.
+The maximum size of
+.IR src_length
+is filesystem dependent and is typically 16MiB.
By convention, the storage used by
.IR src_fd
is mapped into
next reply other threads:[~2016-11-23 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 4:22 Darrick J. Wong [this message]
2016-11-23 4:39 ` [PATCH] fideduperange.2: fix the discussion of maximum sizes Omar Sandoval
2016-11-23 4:47 ` 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=20161123042222.GA30324@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-xfs@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).