From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/1] swapoff01: Define max_runtime 45s
Date: Wed, 4 Sep 2024 12:07:53 +0200 [thread overview]
Message-ID: <20240904100753.GB849136@pevik> (raw)
In-Reply-To: <CAEemH2cg=mk7XzwZj+oYOM5BRzjewE9vHVMnDnX+UmQ4YZTT_g@mail.gmail.com>
> On Wed, Sep 4, 2024 at 5:26 PM Li Wang <liwang@redhat.com> wrote:
> > On Wed, Sep 4, 2024 at 4:53 PM Cyril Hrubis <chrubis@suse.cz> wrote:
> > > Hi!
> > > > > So yes it looks like the actual test needs some runtime defined,
> > > > > although I'm not sure how long it should be. We probably need a
> > > > > reference machine to callibrate this on. I would avoid any emulated CPU
> > > > > and choose a real hardware. I guess one of the RPis e.g. Pi Zero would
> > > > > be a good choice since they are widely available and slow by any modern
> > > > > standards.
Pi Zero is good that it's slow enough that even emulated risc-v will work.
But OTOH might be more practical to measure on RPI4 or RPI3 (maybe more of us
has RPI4 or RPI3 personally or in CI). I mean unless others have/will buy Pi
Zero you will be forced to do the reference. Also Pi Zero is slow (you need to
compile, thus I will not love to do the measurements.
Also emulated risc-v and Pi Zero will always need to set LTP_RUNTIME_MUL, right?
Or do we want to do measurements that even these will run without
LTP_RUNTIME_MUL? That would help users not having to bother, but increasing
limits for fast devices might not be a good idea.
> > > > This makes sense.
> > > So I dusted off my Pi Zero and indeed the test timeouts there as well.
> > > The ntfs filesystem takes 78s, ext2 29s, exfat 20s. So I would say that
> > I'm wondering which distribution (and kernel version) did you use on raspi-0?
Yes, 78s, ext2 29s, exfat 20s is faster, but that's due Raspberry Pi Zero using
just Broadcom BCM2835 SoC as the first generation Raspberry Pi [1] (32 bit arm).
RPI4 uses Broadcom BCM2711 SoC (64-bit quad-core).
Kind regards,
Petr
[1] https://en.wikipedia.org/wiki/Raspberry_Pi#Processor
> I ask this because we might need to consider the oldest supported systems:
> - https://linux-test-project.readthedocs.io/en/latest/users/supported_systems.html
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-04 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:03 [LTP] [PATCH v2 1/1] swapoff01: Define max_runtime 45s Petr Vorel
2024-09-03 15:15 ` Cyril Hrubis
2024-09-04 5:31 ` Petr Vorel
2024-09-04 8:52 ` Cyril Hrubis
2024-09-04 9:26 ` Li Wang
2024-09-04 9:37 ` Li Wang
2024-09-04 10:07 ` Petr Vorel [this message]
2024-09-04 13:58 ` Cyril Hrubis
2024-09-07 2:05 ` Li Wang
2024-09-09 2:52 ` [LTP] [PATCH v3] swapoff01/swapon01: Define max_runtime 1 mins Li Wang
2024-09-09 11:05 ` Avinesh Kumar
2024-09-09 11:46 ` Jan Stancek
2024-09-09 12:54 ` Cyril Hrubis
2024-09-09 14:02 ` Li Wang
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=20240904100753.GB849136@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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