From: Eryu Guan <guan@eryu.me>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2 0/5] generic: add a couple of MMAP CoW tests
Date: Sun, 7 Nov 2021 21:31:43 +0800 [thread overview]
Message-ID: <YYfVP7HJDNGwo8p5@desktop> (raw)
In-Reply-To: <20211105045222.157826-1-ruansy.fnst@fujitsu.com>
On Fri, Nov 05, 2021 at 12:52:17PM +0800, Shiyang Ruan wrote:
> There is a set of CoW tests which is to
> > Check what happens if we BufferedIO/DIO CoW blocks 2-4 of a page's worth
> > of blocks when the second block is a regular/unwritten/hole/delalloc/all
> > block.
> I think a test of MMAP CoW is also needed for these kind of testsets. So,
> add MMAP CoW for each case.
>
> Shiyang Ruan (5):
> generic/xxx: Add MMAP CoW test for 'regular' case
> generic/xxx: Add MMAP CoW test for 'unwritten' case
> generic/xxx: Add MMAP CoW test for 'hole' case
> generic/xxx: Add MMAP CoW test for 'delalloc' case
> generic/xxx: Add MMAP CoW test for 'all' case
Thanks for all these tests!
You could remove the 'xxx' part from patch summary, and for new tests
you don't have to write the specific test seq number in summary,
something like below is fine
generic: add mmap CoW test for 'regular' case
As test seq number will always change on commit, there's no need to keep
such a place holder.
Thanks,
Eryu
>
> tests/generic/900 | 75 +++++++++++++++++++++++
> tests/generic/900.out | 6 ++
> tests/generic/901 | 76 ++++++++++++++++++++++++
> tests/generic/901.out | 6 ++
> tests/generic/902 | 70 ++++++++++++++++++++++
> tests/generic/902.out | 6 ++
> tests/generic/903 | 76 ++++++++++++++++++++++++
> tests/generic/903.out | 6 ++
> tests/generic/904 | 135 ++++++++++++++++++++++++++++++++++++++++++
> tests/generic/904.out | 82 +++++++++++++++++++++++++
> 10 files changed, 538 insertions(+)
> create mode 100755 tests/generic/900
> create mode 100644 tests/generic/900.out
> create mode 100755 tests/generic/901
> create mode 100644 tests/generic/901.out
> create mode 100755 tests/generic/902
> create mode 100644 tests/generic/902.out
> create mode 100755 tests/generic/903
> create mode 100644 tests/generic/903.out
> create mode 100755 tests/generic/904
> create mode 100644 tests/generic/904.out
>
> --
> 2.33.0
>
>
next prev parent reply other threads:[~2021-11-07 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 4:52 [PATCH v2 0/5] generic: add a couple of MMAP CoW tests Shiyang Ruan
2021-11-05 4:52 ` [PATCH v2 1/5] generic/xxx: Add MMAP CoW test for 'regular' case Shiyang Ruan
2021-11-05 16:15 ` Darrick J. Wong
2021-11-05 4:52 ` [PATCH v2 2/5] generic/xxx: Add MMAP CoW test for 'unwritten' case Shiyang Ruan
2021-11-05 16:20 ` Darrick J. Wong
2021-11-08 6:18 ` Shiyang Ruan
2021-11-08 18:08 ` Darrick J. Wong
2021-11-05 4:52 ` [PATCH v2 3/5] generic/xxx: Add MMAP CoW test for 'hole' case Shiyang Ruan
2021-11-05 16:40 ` Darrick J. Wong
2021-11-08 6:33 ` Shiyang Ruan
2021-11-05 4:52 ` [PATCH v2 4/5] generic/xxx: Add MMAP CoW test for 'delalloc' case Shiyang Ruan
2021-11-05 16:42 ` Darrick J. Wong
2021-11-05 4:52 ` [PATCH v2 5/5] generic/xxx: Add MMAP CoW test for 'all' case Shiyang Ruan
2021-11-05 16:49 ` Darrick J. Wong
2021-11-07 13:31 ` Eryu Guan [this message]
2021-11-08 6:25 ` [PATCH v2 0/5] generic: add a couple of MMAP CoW tests Shiyang Ruan
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=YYfVP7HJDNGwo8p5@desktop \
--to=guan@eryu.me \
--cc=fstests@vger.kernel.org \
--cc=ruansy.fnst@fujitsu.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