From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it, NeilBrown <neilb@suse.de>, linux-nfs@vger.kernel.org
Subject: Re: [LTP] [PATCH v4 3/4] nfs05.sh: Lower down the default values
Date: Wed, 3 May 2023 12:08:15 +0200 [thread overview]
Message-ID: <20230503100815.GA3716045@pevik> (raw)
In-Reply-To: <20230428170330.GA3536627@pevik>
Hi all,
> Hi all,
> > nfs05_make_tree.c runs make which needs on Btrfs quite a lot of
> > temporary space. This is a preparation for the next commit which
> > start using all filesystems via TST_ALL_FILESYSTEMS=1. Currently we use
> > 300 MB, which was not enough for Btrfs:
> Also, based on this detection we could add support for tst_device acquire SIZE
> into tst_test.sh to support more than the default 300 MB (as we see the actual
> use is obviously less for some filesystems). This would need to check size with
> tst_fs_has_free.
> Even we don't add this feature, it'd be more friendly to check for space
> before creating the loop device:
> if ! tst_fs_has_free $TST_TMPDIR 300MB; then
> tst_brkm TCONF "Insufficient disk space to create a backing file for loop device"
> fi
> To be honest, I'd like to merge this patchset first, the rest can wait after the
> release.
> Kind regards,
> Petr
> > Filesystem Type Size Used Avail Use% Mounted on
> > /dev/loop0 btrfs 300M 62M 20K 100% /tmp/LTP_nfs05.Vau10kcszO/mntpoint
> > After lowering the default values 96% (58M) is being used.
> > Proper solution would be to detect available size in nfs05_make_tree.c
> > and lower down values based on free space.
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > New in v4.
> > testcases/network/nfs/nfs_stress/nfs05.sh | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> > diff --git a/testcases/network/nfs/nfs_stress/nfs05.sh b/testcases/network/nfs/nfs_stress/nfs05.sh
> > index c18ef1ab4..34151b67a 100755
> > --- a/testcases/network/nfs/nfs_stress/nfs05.sh
> > +++ b/testcases/network/nfs/nfs_stress/nfs05.sh
> > @@ -8,8 +8,8 @@
> > # Created by: Robbie Williamson (robbiew@us.ibm.com)
> > -DIR_NUM=${DIR_NUM:-"10"}
> > -FILE_NUM=${FILE_NUM:-"30"}
> > +DIR_NUM=${DIR_NUM:-"8"}
> > +FILE_NUM=${FILE_NUM:-"28"}
In the end these values are needed, when testing on systems with 64KB page size:
DIR_NUM=${DIR_NUM:-"5"}
FILE_NUM=${FILE_NUM:-"20"}
THREAD_NUM=${THREAD_NUM:-"5"}
Looking at PAGE_SIZE_LESS_THAN_256KB, CONFIG_PAGE_SIZE_LESS_THAN_256KB (option
for all archs) and checking arch dependent configs I see that there can be 4KB,
8KB, 16KB, 32KB, 64KB, 256KB (each arch allows only some of them). Also
filesystems evolve, thus finding safe value for *all* filesystems on different
page sizes on different kernel versions might be a bit complicated.
Kind regards,
Petr
> > THREAD_NUM=${THREAD_NUM:-"8"}
> > TST_NEEDS_CMDS="make gcc"
> > TST_TESTFUNC="do_test"
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-05-03 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 16:00 [LTP] [PATCH v4 0/4] NFS: test on all filesystems Petr Vorel
2023-04-28 16:00 ` [LTP] [PATCH v4 1/4] nfs_lib.sh: Cleanup local and remote directories setup Petr Vorel
2023-04-28 16:00 ` [LTP] [PATCH v4 2/4] nfs_lib.sh: Unexport on proper side on netns Petr Vorel
2023-04-28 16:00 ` [LTP] [PATCH v4 3/4] nfs05.sh: Lower down the default values Petr Vorel
2023-04-28 17:03 ` Petr Vorel
2023-05-03 10:08 ` Petr Vorel [this message]
2023-04-28 16:00 ` [LTP] [PATCH v4 4/4] nfs: Run on all filesystems Petr Vorel
2023-05-02 15:16 ` Petr Vorel
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=20230503100815.GA3716045@pevik \
--to=pvorel@suse.cz \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=neilb@suse.de \
/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