From: Luo Fenglin <luofenglin1@huawei.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v1] sched/sched_stress:Modify sched driver param to run long term testcases
Date: Fri, 16 Oct 2020 17:51:14 +0800 [thread overview]
Message-ID: <1602841876-91490-1-git-send-email-luofenglin1@huawei.com> (raw)
From: luofenglin <luofenglin1@huawei.com>
Add sched_driver process slots param to 10, then long term testcases can run.
Additionally, add sched_driver run time 0.05 hour, long term testcases
run 1/5 of total time.
Signed-off-by: luofenglin <luofenglin1@huawei.com>
---
testcases/kernel/sched/sched_stress/sched_driver.c | 6 +++++-
testcases/kernel/sched/sched_stress/sched_stress.sh | 3 ++-
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/sched/sched_stress/sched_driver.c b/testcases/kernel/sched/sched_stress/sched_driver.c
index 61573d788..1bee9d130 100644
--- a/testcases/kernel/sched/sched_stress/sched_driver.c
+++ b/testcases/kernel/sched/sched_stress/sched_driver.c
@@ -202,8 +202,12 @@ int main(int argc, char **argv)
/*
* Start the long-term testcases running
+ * Run time set 1/5 of total
*/
- start_long_term_testcases(long_term_slot_total, argv[2]);
+ char run_long_term_time[20];
+ int runlongtime = runseconds / 5;
+ sprintf(run_long_term_time, "%d", runlongtime);
+ start_long_term_testcases(long_term_slot_total, run_long_term_time);
short_term_slot_total = workslots / 2;
fflush(stdout);
diff --git a/testcases/kernel/sched/sched_stress/sched_stress.sh b/testcases/kernel/sched/sched_stress/sched_stress.sh
index 797d0601b..0205446a7 100755
--- a/testcases/kernel/sched/sched_stress/sched_stress.sh
+++ b/testcases/kernel/sched/sched_stress/sched_stress.sh
@@ -30,6 +30,7 @@ export KERNEL=./sched_datafile
touch $KERNEL
echo 0.000000 > sch.measure
export RAWDEV=`df / | grep dev | awk {'print $1'}`
-sched_driver -s 0.9 -t 0.02 -p 2 > /tmp/tmp$$
+echo "Result file: /tmp/tmp$$"
+sched_driver -s 0.9 -t 0.05 -p 10 -d > /tmp/tmp$$
tail -n 5 /tmp/tmp$$
rm -rf /tmp/tmp$$ ./sched_datafile sch.measure
--
2.17.1
next reply other threads:[~2020-10-16 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 9:51 Luo Fenglin [this message]
2020-10-16 9:51 ` [LTP] [PATCH v2] sched/sched_stress:Fixed param of sched_tc Luo Fenglin
2021-01-06 10:29 ` Cyril Hrubis
2020-10-16 9:51 ` [LTP] [PATCH v3] sched/sched_stress:Bugfix for setting real time priority Luo Fenglin
2021-01-06 10:44 ` Cyril Hrubis
2021-01-06 10:25 ` [LTP] [PATCH v1] sched/sched_stress:Modify sched driver param to run long term testcases Cyril Hrubis
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=1602841876-91490-1-git-send-email-luofenglin1@huawei.com \
--to=luofenglin1@huawei.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