From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
fstests@vger.kernel.org
Cc: djwong@kernel.org, mcgrof@kernel.org, gost.dev@samsung.com,
zlang@redhat.com, kernel@pankajraghav.com,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH v3 3/3] xfs/008: use block size instead of the pagesize
Date: Mon, 27 May 2024 22:33:16 +0530 [thread overview]
Message-ID: <87le3v5grv.fsf@gmail.com> (raw)
In-Reply-To: <20240527114834.167521-4-kernel@pankajraghav.com>
"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com> writes:
> From: Pankaj Raghav <p.raghav@samsung.com>
>
> The testcase estimates to have ratio of 1:3/4 for holes:filesize. This
> holds true where the blocksize is always less than or equal to pagesize
> and the total size of the file is calculated based on the pagesize.
> There is an implicit assumption that blocksize will always be less than
> the pagesize.
>
> LBS support will enable bs > ps where a minimum IO size is one block,
> which can be greater than a page. Adjust the size calculation to be
> based on the blocksize and not the pagesize.
Thanks for addressing the comments. I agree it should be just blocksize
itself. Even the randholes.c only takes -b blocksize.
(Minor nit below)
Looks good to me. Please feel free to add -
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
> tests/xfs/008 | 20 +++++++++-----------
> tests/xfs/008.out | 8 ++++----
> 2 files changed, 13 insertions(+), 15 deletions(-)
>
> diff --git a/tests/xfs/008 b/tests/xfs/008
> index e7d6153b..f42b3ac8 100755
> --- a/tests/xfs/008
> +++ b/tests/xfs/008
> @@ -10,8 +10,7 @@
> _begin_fstest rw ioctl auto quick
>
> status=0 # success is the default!
> -pgsize=`$here/src/feature -s`
> -
> +blksize=$(_get_file_block_size "$TEST_DIR")
nit: maybe we should move blksize calculation to after _require_test ??
> # Override the default cleanup function.
> _cleanup()
> {
> @@ -21,7 +20,7 @@ _cleanup()
>
> _filter()
> {
> - sed -e "s/-b $pgsize/-b PGSIZE/g" \
> + sed -e "s/-b $blksize/-b BLKSIZE/g" \
> -e "s/-l .* -c/-l FSIZE -c/g"
> }
>
> @@ -73,18 +72,17 @@ _require_test
> # We are trying to create roughly 50 or 100 holes in a file
> # using random writes. Assuming a good distribution of 50 writes
> # in a file, the file only needs to be 3-4x the size of the write
> -# size muliplied by the number of writes. Hence we use 200 * pgsize
> -# for files we want 50 holes in and 400 * pgsize for files we want
> +# size muliplied by the number of writes. Hence we use 200 * blksize
> +# for files we want 50 holes in and 400 * blksize for files we want
> # 100 holes in. This keeps the runtime down as low as possible.
> #
> -_do_test 1 50 "-l `expr 200 \* $pgsize` -c 50 -b $pgsize"
> -_do_test 2 100 "-l `expr 400 \* $pgsize` -c 100 -b $pgsize"
> -_do_test 3 100 "-l `expr 400 \* $pgsize` -c 100 -b 512" # test partial pages
> +_do_test 1 50 "-l `expr 200 \* $blksize` -c 50 -b $blksize"
> +_do_test 2 100 "-l `expr 400 \* $blksize` -c 100 -b $blksize"
> +_do_test 3 100 "-l `expr 400 \* $blksize` -c 100 -b 512" # test partial blocks
>
> # rinse, lather, repeat for direct IO
> -_do_test 4 50 "-d -l `expr 200 \* $pgsize` -c 50 -b $pgsize"
> -_do_test 5 100 "-d -l `expr 400 \* $pgsize` -c 100 -b $pgsize"
> -# note: direct IO requires page aligned IO
> +_do_test 4 50 "-d -l `expr 200 \* $blksize` -c 50 -b $blksize"
> +_do_test 5 100 "-d -l `expr 400 \* $blksize` -c 100 -b $blksize"
>
> # todo: realtime.
>
> diff --git a/tests/xfs/008.out b/tests/xfs/008.out
> index 5e3ae8e3..0941e218 100644
> --- a/tests/xfs/008.out
> +++ b/tests/xfs/008.out
> @@ -1,10 +1,10 @@
> QA output created by 008
>
> -randholes.1 : -l FSIZE -c 50 -b PGSIZE
> +randholes.1 : -l FSIZE -c 50 -b BLKSIZE
> ------------------------------------------
> holes is in range
>
> -randholes.2 : -l FSIZE -c 100 -b PGSIZE
> +randholes.2 : -l FSIZE -c 100 -b BLKSIZE
> ------------------------------------------
> holes is in range
>
> @@ -12,10 +12,10 @@ randholes.3 : -l FSIZE -c 100 -b 512
> ------------------------------------------
> holes is in range
>
> -randholes.4 : -d -l FSIZE -c 50 -b PGSIZE
> +randholes.4 : -d -l FSIZE -c 50 -b BLKSIZE
> ------------------------------------------
> holes is in range
>
> -randholes.5 : -d -l FSIZE -c 100 -b PGSIZE
> +randholes.5 : -d -l FSIZE -c 100 -b BLKSIZE
> ------------------------------------------
> holes is in range
> --
> 2.34.1
prev parent reply other threads:[~2024-05-27 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 11:48 [PATCH v3 0/3] more lbs test fixes Pankaj Raghav (Samsung)
2024-05-27 11:48 ` [PATCH v3 1/3] xfs/161: adapt the test case for 64k FS blocksize Pankaj Raghav (Samsung)
2024-05-27 11:48 ` [PATCH v3 2/3] generic/436: round up bufsz to nearest filesystem blksz Pankaj Raghav (Samsung)
2024-05-27 13:01 ` Pankaj Raghav (Samsung)
2024-05-27 13:26 ` Zorro Lang
2024-05-28 9:12 ` Pankaj Raghav (Samsung)
2024-05-27 11:48 ` [PATCH v3 3/3] xfs/008: use block size instead of the pagesize Pankaj Raghav (Samsung)
2024-05-27 17:03 ` Ritesh Harjani [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=87le3v5grv.fsf@gmail.com \
--to=ritesh.list@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=kernel@pankajraghav.com \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=zlang@redhat.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