From: Brian Foster <[email protected]>
To: Zorro Lang <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH 2/3] generic: fsx IO_URING soak tests
Date: Fri, 2 Oct 2020 14:20:22 -0400 [thread overview]
Message-ID: <20201002182022.GD4708@bfoster> (raw)
In-Reply-To: <[email protected]>
On Thu, Sep 17, 2020 at 01:14:42AM +0800, Zorro Lang wrote:
> After fsx supports IO_URING read/write, add a test to do IO_URING
> soak test of fsx.
>
> Signed-off-by: Zorro Lang <[email protected]>
> ---
> common/rc | 16 ++++++++++++
> tests/generic/609 | 58 +++++++++++++++++++++++++++++++++++++++++++
> tests/generic/609.out | 2 ++
> tests/generic/group | 1 +
> 4 files changed, 77 insertions(+)
> create mode 100755 tests/generic/609
> create mode 100644 tests/generic/609.out
>
...
> diff --git a/tests/generic/609 b/tests/generic/609
> new file mode 100755
> index 00000000..1d9b6fed
> --- /dev/null
> +++ b/tests/generic/609
> @@ -0,0 +1,58 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2020 Red Hat Inc. All Rights Reserved.
> +#
> +# FS QA Test 609
> +#
> +# IO_URING soak buffered fsx test
> +#
> +seq=`basename $0`
> +seqres=$RESULT_DIR/$seq
> +echo "QA output created by $seq"
> +
> +here=`pwd`
> +tmp=/tmp/$$
> +status=1 # failure is the default!
> +trap "_cleanup; exit \$status" 0 1 2 3 15
> +
> +_cleanup()
> +{
> + cd /
> + rm -f $tmp.*
> +}
> +
> +# get standard environment, filters and checks
> +. ./common/rc
> +. ./common/filter
> +
> +# remove previous $seqres.full before test
> +rm -f $seqres.full
> +
> +# real QA test starts here
> +
> +# Modify as appropriate.
> +_supported_fs generic
> +_supported_os Linux
> +_require_test
> +_require_io_uring
> +
> +# Run fsx for a million ops or more
> +nr_ops=$((100000 * TIME_FACTOR))
The value used here doesn't match the comment. Though it looks like this
is modeled after generic/512, which does specify 1m ops, but also isn't
included in the auto group presumably due to the time required to run
the test.
Brian
> +op_sz=$((128000 * LOAD_FACTOR))
> +file_sz=$((600000 * LOAD_FACTOR))
> +fsx_file=$TEST_DIR/fsx.$seq
> +
> +fsx_args=(-S 0)
> +fsx_args+=(-U)
> +fsx_args+=(-q)
> +fsx_args+=(-N $nr_ops)
> +fsx_args+=(-p $((nr_ops / 100)))
> +fsx_args+=(-o $op_sz)
> +fsx_args+=(-l $file_sz)
> +
> +run_fsx "${fsx_args[@]}" | sed -e '/^fsx.*/d'
> +
> +# success, all done
> +echo "Silence is golden"
> +status=0
> +exit
> diff --git a/tests/generic/609.out b/tests/generic/609.out
> new file mode 100644
> index 00000000..0d75b384
> --- /dev/null
> +++ b/tests/generic/609.out
> @@ -0,0 +1,2 @@
> +QA output created by 609
> +Silence is golden
> diff --git a/tests/generic/group b/tests/generic/group
> index aa969bcb..cf50f4a1 100644
> --- a/tests/generic/group
> +++ b/tests/generic/group
> @@ -611,3 +611,4 @@
> 606 auto attr quick dax
> 607 auto attr quick dax
> 608 auto attr quick dax
> +609 auto rw io_uring
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-10-02 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 17:14 [PATCH 0/3] xfstests: add IO_URING test cases Zorro Lang
2020-09-16 17:14 ` [PATCH 1/3] src/feature: add IO_URING feature checking Zorro Lang
2020-10-02 18:19 ` Brian Foster
2020-09-16 17:14 ` [PATCH 2/3] generic: fsx IO_URING soak tests Zorro Lang
2020-10-02 18:20 ` Brian Foster [this message]
2020-09-16 17:14 ` [PATCH 3/3] generic: IO_URING direct IO fsx test Zorro Lang
2020-10-02 18:20 ` Brian Foster
2020-10-05 16:45 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2020-09-16 13:11 [PATCH 0/3] xfstests: new io_uring " Zorro Lang
2020-09-16 13:11 ` [PATCH 2/3] generic: fsx IO_URING soak tests Zorro Lang
2020-09-16 12:30 [PATCH 0/3] xfstests: new io_uring fsx test Zorro Lang
2020-09-16 12:30 ` [PATCH 2/3] generic: fsx IO_URING soak tests Zorro Lang
2020-09-16 12:23 [PATCH 0/3] src/feature: add IO_URING feature checking Zorro Lang
2020-09-16 12:23 ` [PATCH 2/3] generic: fsx IO_URING soak tests Zorro Lang
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=20201002182022.GD4708@bfoster \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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