From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-xfs@vger.kernel.org, "Darrick J . Wong" <djwong@kernel.org>,
automated-testing@yoctoproject.org, ltp@lists.linux.it,
automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [RFC PATCH 1/1] API: Allow to use xfs filesystems < 300 MB
Date: Thu, 18 Aug 2022 11:53:08 +0200 [thread overview]
Message-ID: <Yv4MBF79PnJKJbwm@yuki> (raw)
In-Reply-To: <20220817204015.31420-1-pvorel@suse.cz>
Hi!
I'm starting to wonder if we should start tracking minimal FS size per
filesystem since btrfs and xfs will likely to continue to grow and with
that we will end up disabling the whole fs related testing on embedded
boards with a little disk space. If we tracked that per filesystem we
would be able to skip a subset of filesystems when there is not enough
space. The downside is obviously that we would have to add a bit more
complexity to the test library.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-18 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 20:40 [LTP] [RFC PATCH 1/1] API: Allow to use xfs filesystems < 300 MB Petr Vorel
2022-08-17 23:59 ` Darrick J. Wong
2022-08-18 5:08 ` Amir Goldstein
2022-08-18 9:45 ` Petr Vorel
2022-08-18 9:01 ` Petr Vorel
2022-08-18 9:53 ` Cyril Hrubis [this message]
2022-08-18 11:12 ` Petr Vorel
2022-08-18 11:30 ` Cyril Hrubis
2022-08-18 11:55 ` [LTP] [Automated-testing] " Geert Uytterhoeven
2022-08-19 19:28 ` Petr Vorel
2022-08-20 2:37 ` Li Wang
2022-08-22 9:36 ` Petr Vorel
2022-08-20 2:52 ` [LTP] " Li Wang
2022-08-24 10:21 ` Petr Vorel
2022-08-29 1:45 ` Li Wang
2024-04-03 14:24 ` 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=Yv4MBF79PnJKJbwm@yuki \
--to=chrubis@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=automated-testing@yoctoproject.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).