From: Brian Foster <bfoster@redhat.com>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH v2 4/4] fsx: move range generation logic into a common helper
Date: Fri, 17 Apr 2020 13:10:50 -0400 [thread overview]
Message-ID: <20200417171050.GE13463@bfoster> (raw)
In-Reply-To: <20200408181208.12054-1-fdmanana@kernel.org>
On Wed, Apr 08, 2020 at 07:12:08PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> We have very similar code that generates the destination range for clone,
> dedupe and copy_file_range operations, so avoid duplicating the code three
> times and move it into a helper function.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
>
> V2: Turned the first parameter of the helper into a boolean as Darrick suggested.
>
> ltp/fsx.c | 91 +++++++++++++++++++++++++--------------------------------------
> 1 file changed, 36 insertions(+), 55 deletions(-)
>
> diff --git a/ltp/fsx.c b/ltp/fsx.c
> index 89a5f60e..9bfc98e0 100644
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
...
> @@ -2004,63 +2034,14 @@ test(void)
> keep_size = random() % 2;
> break;
...
> case OP_COPY_RANGE:
> - {
> - int tries = 0;
> -
> - TRIM_OFF_LEN(offset, size, file_size);
> - offset -= offset % readbdy;
> - if (o_direct)
> - size -= size % readbdy;
> - do {
> - if (tries++ >= 30) {
> - size = 0;
> - break;
> - }
> - offset2 = random();
> - TRIM_OFF(offset2, maxfilelen);
> - offset2 -= offset2 % writebdy;
It looks like this writebdy bit is lost in the new helper...
Brian
> - } while (range_overlaps(offset, offset2, size) ||
> - offset2 + size > maxfilelen);
> - break;
> - }
> + generate_dest_range(true, maxfilelen, &offset, &size, &offset2);
> + break;
> }
>
> have_op:
> --
> 2.11.0
>
next prev parent reply other threads:[~2020-04-17 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:36 [PATCH 4/4] fsx: move range generation logic into a common helper fdmanana
2020-04-08 15:48 ` Darrick J. Wong
2020-04-08 16:57 ` Filipe Manana
2020-04-08 17:22 ` Darrick J. Wong
2020-04-08 18:12 ` [PATCH v2 " fdmanana
2020-04-17 17:10 ` Brian Foster [this message]
2020-04-17 17:20 ` Filipe Manana
2020-04-17 17:32 ` [PATCH " fdmanana
2020-04-20 14:33 ` Brian Foster
2020-04-20 17:05 ` Filipe Manana
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=20200417171050.GE13463@bfoster \
--to=bfoster@redhat.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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).