From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] (no subject)
Date: Thu, 22 Aug 2019 14:45:12 +0200 [thread overview]
Message-ID: <20190822124512.GB6325@rei> (raw)
In-Reply-To: <CAJwJstDWVJ8HG=Fe1VZtPDTAsCawfoKkdLAikFMQZ-hXhOprvA@mail.gmail.com>
Hi!
> I want to ask if I can use ltp for stressing CPU and Memory with Linux OS?
What kind of stress do you have in mind?
I guess that for CPU stress something as compiling kernel in a loop with
large enough -j parameter will suffice.
There are some test for OOM and memory overcommit, these are part of the
mm runtest file.
> If the answer is yes, Can I get the detailed explanation about the hierachy
> of ltp because I think the document of ltp did not explain that.
Unforunately that part of LTP is undercommented, you have to mostly
explore on your own, sorry.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-08-22 12:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 2:25 [LTP] (no subject) Jim Woo
2019-08-22 12:45 ` Cyril Hrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-14 15:37 Avinesh Kumar
2024-08-14 6:38 Indumathi Raju
2024-08-26 11:50 ` Cyril Hrubis
[not found] <tencent_048887541FB562D43FE2D104@qq.com>
2024-04-28 7:16 ` =?gb18030?B?wrfssw==?=
2024-04-19 7:07 [LTP] [PATCH v2] Add case about arch_prctl syscall lufei
2024-04-21 7:15 ` [LTP] (no subject) lufei
2024-04-26 8:36 ` Cyril Hrubis
2024-04-26 9:42 ` 路斐
2024-04-26 10:28 ` Cyril Hrubis
2024-04-26 12:27 ` 路斐
2024-04-26 12:47 ` Jan Stancek
2024-04-28 7:44 ` lufei
2021-11-15 8:15 Joerg Vehlow
2019-10-07 6:45 Joerg Vehlow
2019-10-07 6:53 ` Joerg Vehlow
2014-03-07 11:39 [LTP] [PATCH 1/2] add tst_get_unused_port() Jan Stancek
2014-03-10 14:22 ` [LTP] (no subject) Jan Stancek
2013-08-05 14:44 Stanislav Kholmanskikh
2009-07-01 20:08 Henry Yei
2009-06-24 22:58 Henry Yei
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=20190822124512.GB6325@rei \
--to=chrubis@suse.cz \
--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