public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it, Li Wang <liwang@redhat.com>,
	Martin Doucha <mdoucha@suse.cz>,
	Richard Palethorpe <rpalethorpe@suse.com>,
	Joerg Vehlow <joerg.vehlow@aox-tech.de>,
	automated-testing@lists.yoctoproject.org,
	Tim Bird <tim.bird@sony.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [Automated-testing] [PATCH 2/6] API: tst_device: Track minimal size per filesystem
Date: Mon, 29 Aug 2022 14:24:36 +0200	[thread overview]
Message-ID: <YwywBFhVtfO6gc0u@yuki> (raw)
In-Reply-To: <YwyjDLcGzhDiWXkD@pevik>

Hi!
> > I do not think that we should harcode this here. I would be for a more
> > dynamic approach, i.e. add a function into the tst_supported_fs_types.c
> > that loops over supported filesystems and chooses max over the minimal
> > values for all supported filesystems. That way if we run on embedded
> > targets the device size will be 16MB as long as btrfs-progs is not
> > installed. Also that way we can easily define minimal size for xfs 300MB
> > and things will work for embedded as long as xfs-progs are not
> > installed.
> Correct. So the value for .all_filesystems should be maximum of supported
> filesystems. The only think I don't like about it that it takes some time to
> check everything (mkfs.* available ... etc), but we can't avoid it.
> 
> Is it worth to cache this value (make it static in the function) so that it's not
> searched more than once?

Actually all we would need is a flag that would just return the pointer
to the fs_types array from the tst_get_supported_fs_types() on second
and subsequent calls.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2022-08-29 12:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  0:28 [PATCH 0/6] Track minimal size per filesystem Petr Vorel
2022-08-27  0:28 ` [PATCH 1/6] tst_fs_type: Add nsfs, vfat, squashfs to tst_fs_type_name() Petr Vorel
2022-08-29 10:44   ` Cyril Hrubis
2022-08-29 15:46   ` Bird, Tim
2022-08-29 16:14     ` Petr Vorel
2022-08-29 16:35       ` Bird, Tim
2022-08-29 16:49         ` Petr Vorel
2022-08-27  0:28 ` [PATCH 2/6] API: tst_device: Track minimal size per filesystem Petr Vorel
2022-08-29 10:58   ` Cyril Hrubis
2022-08-29 11:29     ` Petr Vorel
2022-08-29 12:24       ` Cyril Hrubis [this message]
2022-08-27  0:28 ` [PATCH 3/6] tst_test: Use 16 MB also for tmpfs Petr Vorel
2022-08-29 11:00   ` Cyril Hrubis
2022-08-27  0:28 ` [PATCH 4/6] tst_device: Use getopts Petr Vorel
2022-08-29 11:03   ` [Automated-testing] " Cyril Hrubis
2022-08-29 11:42     ` Petr Vorel
2022-08-27  0:28 ` [PATCH 5/6] tst_device: Add support -f filesystem Petr Vorel
2022-08-29 11:04   ` Cyril Hrubis
2022-08-27  0:28 ` [PATCH 6/6] tst_test.sh: Pass used filesystem to tst_device Petr Vorel
2022-08-29 11:05   ` Cyril Hrubis
2022-08-29 10:43 ` [Automated-testing] [PATCH 0/6] Track minimal size per filesystem Cyril Hrubis
2022-08-29 11:39   ` Petr Vorel
     [not found]     ` <CAEemH2dbBZO91EEB-xheoToUPuz=SBDjp9dGzy1YuVL+qGgOMQ@mail.gmail.com>
2022-08-30  8:18       ` 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=YwywBFhVtfO6gc0u@yuki \
    --to=chrubis@suse.cz \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=joerg.vehlow@aox-tech.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    --cc=pvorel@suse.cz \
    --cc=rpalethorpe@suse.com \
    --cc=tim.bird@sony.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