From: Boaz Harrosh <boaz@plexistor.com>
To: Anna Schumaker <Anna.Schumaker@Netapp.com>, fstests@vger.kernel.org
Cc: linux-nfs@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH v5 2/5] generic/417: Add small copies to new file test
Date: Wed, 22 Mar 2017 18:45:08 +0200 [thread overview]
Message-ID: <dce891e7-b15b-2197-8473-c1012cc2d216@plexistor.com> (raw)
In-Reply-To: <20170317195233.4042-3-Anna.Schumaker@Netapp.com>
On 03/17/2017 09:52 PM, Anna Schumaker wrote:
> This test copies single bytes from a source file into various new files
> just to make sure that we can handle very small copies.
>
Sorry for not following closely, but how is this supposed to work, I know that
for FSs that support it a copy_file_range is supported by clone_file_range.
But usually there are fs-block alignment restrictions on clone_file_range.
Does the VFS do the switch from fs->clone to generic-copy, or is the FS
suppose to call the generic-copy?
Thanks
Boaz
> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
> ---
> tests/generic/417 | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/generic/417.out | 16 ++++++++++
> tests/generic/group | 1 +
> 3 files changed, 100 insertions(+)
> create mode 100755 tests/generic/417
> create mode 100644 tests/generic/417.out
>
> diff --git a/tests/generic/417 b/tests/generic/417
> new file mode 100755
> index 00000000..dde3f4d6
> --- /dev/null
> +++ b/tests/generic/417
> @@ -0,0 +1,83 @@
> +#!/bin/bash
> +# FS QA Test No. 417
> +#
> +# Tests vfs_copy_file_range():
> +# - Copy a small file
> +# - Small copies from various points in the original file
> +#-----------------------------------------------------------------------
> +# Copyright (c) 2016 Netapp, Inc. All rights reserved.
<snip>
next prev parent reply other threads:[~2017-03-22 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 19:52 [PATCH v5 0/5] Add copy_file_range() tests Anna Schumaker
2017-03-17 19:52 ` [PATCH v5 1/5] generic/416: Add copy to new file test Anna Schumaker
2017-03-17 19:52 ` [PATCH v5 2/5] generic/417: Add small copies " Anna Schumaker
2017-03-22 16:45 ` Boaz Harrosh [this message]
2017-03-17 19:52 ` [PATCH v5 3/5] generic/418: Add copy test that overwrites data Anna Schumaker
2017-03-17 19:52 ` [PATCH v5 4/5] generic/419: Add a copy test for overwriting small amounts of data Anna Schumaker
2017-03-17 19:52 ` [PATCH v5 5/5] generic/420: Add a copy test for invalid input Anna Schumaker
2017-03-17 22:02 ` [PATCH v5 0/5] Add copy_file_range() tests Darrick J. Wong
2017-03-20 5:24 ` Eryu Guan
2017-05-02 22:16 ` Darrick J. Wong
2017-05-03 12:56 ` Olga Kornievskaia
2017-05-03 15:48 ` 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=dce891e7-b15b-2197-8473-c1012cc2d216@plexistor.com \
--to=boaz@plexistor.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-nfs@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).