From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: mtk.manpages@gmail.com, 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: Re: [PATCH] fideduperange.2: fix the discussion of maximum sizes
Date: Tue, 22 Nov 2016 20:47:26 -0800 [thread overview]
Message-ID: <20161123044726.GF16807@birch.djwong.org> (raw)
In-Reply-To: <20161123043918.GD29697@mew>
On Tue, Nov 22, 2016 at 08:39:18PM -0800, Omar Sandoval wrote:
> On Tue, Nov 22, 2016 at 08:22:22PM -0800, Darrick J. Wong wrote:
> > 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
>
> Might be worth it to clarify that the file_dedupe_range_info limit is a
> hard limit that will result in an error if exceeded and that the
> src_length limit is silently enforced. These semantics suck...
Yeah... :(
Anyway I'll post a v2 patch.
--D
>
> --
> Omar
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-11-23 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 4:22 [PATCH] fideduperange.2: fix the discussion of maximum sizes Darrick J. Wong
2016-11-23 4:39 ` Omar Sandoval
2016-11-23 4:47 ` Darrick J. Wong [this message]
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=20161123044726.GF16807@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 \
--cc=osandov@osandov.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).