From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] Add test for data integrity over NFS
Date: Mon, 2 Dec 2024 15:36:22 +0100 [thread overview]
Message-ID: <20241202143622.GA321427@pevik> (raw)
In-Reply-To: <20241129133421.24349-1-mdoucha@suse.cz>
Hi Martin,
...
> +TST_CNT=4
> +TST_TESTFUNC="do_test"
> +TST_DEVICE_SIZE=1024
> +TST_TIMEOUT=2400
It looks like block size (f_bsize member of struct statvfs) differs depending on
RAM. Testing on s390x VM:
* 1 GB => block size: 131072
* 2 GB => block size: 262144
* 4 GB => block size: 524288
This can cause timeouts depending on the machine setup.
How about changing TST_TIMEOUT=-1 ? I don't like unlimited setup, but in this
case I would keep it. Timeout is handled by fsplough.c anyway.
If you agree, I can change during merge.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Kind regards,
Petr
> +
> +do_test1()
> +{
> + tst_res TINFO "Testing buffered write, buffered read"
> + EXPECT_PASS fsplough -c 512 -d "$PWD"
> +}
> +
> +do_test2()
> +{
> + tst_res TINFO "Testing buffered write, direct read"
> + EXPECT_PASS fsplough -c 512 -R -d "$PWD"
> +}
> +
> +do_test3()
> +{
> + tst_res TINFO "Testing direct write, buffered read"
> + EXPECT_PASS fsplough -c 512 -W -d "$PWD"
> +}
> +
> +do_test4()
> +{
> + tst_res TINFO "Testing direct write, direct read"
> + EXPECT_PASS fsplough -c 512 -RW -d "$PWD"
> +}
> +
> +. nfs_lib.sh
> +tst_run
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-12-02 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 13:34 [LTP] [PATCH v2] Add test for data integrity over NFS Martin Doucha
2024-12-02 14:36 ` Petr Vorel [this message]
2024-12-06 11:43 ` Cyril Hrubis
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=20241202143622.GA321427@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.