From: Zorro Lang <zlang@redhat.com>
To: Pavel Reichl <preichl@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2 2/2] g/299: skip test early if falloc is not supported
Date: Thu, 29 Sep 2022 10:04:47 +0800 [thread overview]
Message-ID: <20220929020447.c6hspjc2ju3ax3a7@zlang-mailbox> (raw)
In-Reply-To: <20220922185502.1046115-2-preichl@redhat.com>
On Thu, Sep 22, 2022 at 08:55:02PM +0200, Pavel Reichl wrote:
> Move the _require_xfs_io_command "falloc" above the
> potencially 'expensive' function _get_max_file_size
>
> Signed-off-by: Pavel Reichl <preichl@redhat.com>
> ---
Hmm... looks like the `_require_xfs_io_command "falloc"` helps to save a helper
"_require_falloc" which detects if fs (kernel part) supports fallocate, although
it trys to make sure xfs_io supports falloc command.
Reviewed-by: Zorro Lang <zlang@redhat.com>
Thanks,
Zorro
> tests/generic/299 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/generic/299 b/tests/generic/299
> index 8e1a112c..1bb371a3 100755
> --- a/tests/generic/299
> +++ b/tests/generic/299
> @@ -24,6 +24,7 @@ _require_scratch
> _require_odirect
> _require_aio
> _require_block_device $SCRATCH_DEV
> +_require_xfs_io_command "falloc"
>
> NUM_JOBS=$((4*LOAD_FACTOR))
> BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV`
> @@ -96,7 +97,6 @@ filename=buffered-aio-verifier
> EOF
>
> _require_fio $fio_config
> -_require_xfs_io_command "falloc"
>
> _scratch_mkfs >> $seqres.full 2>&1
> _scratch_mount
> --
> 2.37.3
>
next prev parent reply other threads:[~2022-09-29 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 18:55 [PATCH v2 1/2] clean-up; Remove left files after test finishes Pavel Reichl
2022-09-22 18:55 ` [PATCH v2 2/2] g/299: skip test early if falloc is not supported Pavel Reichl
2022-09-29 2:04 ` Zorro Lang [this message]
2022-09-29 1:58 ` [PATCH v2 1/2] clean-up; Remove left files after test finishes 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=20220929020447.c6hspjc2ju3ax3a7@zlang-mailbox \
--to=zlang@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=preichl@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