From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Tobias Schaffner <tobias.schaffner@siemens.com>, xenomai@lists.linux.dev
Subject: Re: [libevl][PATCH 1/4] Copy dohell from Xenomai 3
Date: Thu, 13 Jun 2024 17:55:02 +0200 [thread overview]
Message-ID: <877cesrfir.fsf@xenomai.org> (raw)
In-Reply-To: <fb5efca7-cba3-4115-86be-0b719c5a74b4@siemens.com>
Jan Kiszka <jan.kiszka@siemens.com> writes:
> On 13.06.24 16:23, Philippe Gerum wrote:
>>
>> Tobias Schaffner <tobias.schaffner@siemens.com> writes:
>>
>>> Dohell is used as the default load generator in Xenomai 3. Add it to
>>> libevl to be able to stress the system while testing evl.
>>>
>>
>> dohell is obsolete. Let's move to stress-ng or something alike for x4.
>>
>
> See my comment on patch 3: If you can name a configuration of stress-ng
> that stresses a co-kernel more than what dohell does, we can take it.
> Otherwise, I would strongly recommend to not do less hell over here.
>
The most important stress dohell applies is basically hackbench and a dd
loop trashing the D-cache. The latter can be obtained with a combo of
VM+I/O tests from stress-ng. So basically, the whole issue boils down to
having hackbench on board, provided we cannot generate the same load
profile with stress-ng with a CPU bound stressor. Besides, I never saw
any added value in running ltp tests compared to a combo of stress-ng
stressors when it comes to latency testing.
We obviously don't want to throw less hell, but throwing more obsolete
stuff is not an option either. So that's a NAK for v4 ATM, I'll gather
more information about how we could leverage stress-ng in order to
compare to dohell. This is worth a shot.
--
Philippe.
next prev parent reply other threads:[~2024-06-13 16:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:45 [libevl][PATCH 0/4] evl-test: align with xeno-test Tobias Schaffner
2024-06-13 13:45 ` [libevl][PATCH 1/4] Copy dohell from Xenomai 3 Tobias Schaffner
2024-06-13 14:23 ` Philippe Gerum
2024-06-13 15:32 ` Jan Kiszka
2024-06-13 15:55 ` Philippe Gerum [this message]
2025-09-02 9:51 ` Jorge Ramirez-Ortiz, Gmail
2024-06-13 13:45 ` [libevl][PATCH 2/4] evl-test: Measure worst case latencies Tobias Schaffner
2024-06-13 14:09 ` Philippe Gerum
2024-06-13 13:45 ` [libevl][PATCH 3/4] evl-test: Start evl-test with load by default Tobias Schaffner
2024-06-13 14:16 ` Philippe Gerum
2024-06-13 15:30 ` Jan Kiszka
2024-06-13 16:09 ` Philippe Gerum
2024-11-01 17:00 ` Jorge Ramirez-Ortiz, Gmail
2024-11-18 7:48 ` Jan Kiszka
2024-11-18 8:26 ` Philippe Gerum
2025-09-01 18:46 ` Tobias Schaffner
2024-06-13 17:27 ` Philippe Gerum
2024-06-14 7:29 ` Jorge Ramirez-Ortiz, Gmail
2024-07-10 7:18 ` Tobias Schaffner
2024-10-24 20:00 ` Schaffner, Tobias
2024-10-27 19:13 ` Jorge Ramirez-Ortiz, Gmail
2024-11-01 16:55 ` Jorge Ramirez-Ortiz, Gmail
2024-11-01 17:15 ` Philippe Gerum
2024-11-01 18:13 ` Jorge Ramirez-Ortiz, Gmail
2025-09-03 5:29 ` Jan Kiszka
2025-09-03 8:12 ` Jorge Ramirez-Ortiz, Gmail
2025-09-03 8:20 ` Florian Bezdeka
2025-09-03 8:45 ` Jorge Ramirez-Ortiz, Gmail
2025-09-03 9:12 ` Florian Bezdeka
2024-06-13 13:45 ` [libevl][PATCH 4/4] evl-test: Add hectic for real-time stress Tobias Schaffner
2024-06-13 14:26 ` Philippe Gerum
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=877cesrfir.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=tobias.schaffner@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.