From: Shi Weihua <shiwh@cn.fujitsu.com>
To: ltp-list <ltp-list@lists.sourceforge.net>
Subject: [LTP] [PATCH] cpuctl_fj: replace ps by top to fix cpu usage's computation error
Date: Wed, 06 Jan 2010 12:58:37 +0800 [thread overview]
Message-ID: <4B44187D.5030702@cn.fujitsu.com> (raw)
Some abnormal messages outputted in my x86_64.
-------------------
pid 4622 cpu_usage 0
cpuctl_test_fj 1 TFAIL : case19 FAIL
pid 4646 cpu_usage 0
cpuctl_test_fj 1 TFAIL : case20 FAIL
pid 4670 cpu_usage 63
cpuctl_test_fj 1 TFAIL : case21 FAIL
-------------------
I think cpu usage's computation error occured.
So I tried to use the oldest arithmetic of cpu usage, fortunately it works.
Maybe we should replace 'ps' by 'top' in get_cpu_usage().
By the way, I increased the admissible range of cpu usage in case21()
because it jumps out range of 44-56 sometimes.
My patch works now:
-------------------
pid 20277 cpu_usage 97
cpuctl_test_fj 1 TPASS : case19 PASS
pid 20307 cpu_usage 99
cpuctl_test_fj 1 TPASS : case20 PASS
pid 20336 cpu_usage 55
pid 20336 cpu_usage 53
pid 20336 cpu_usage 55
pid 20336 cpu_usage 57
pid 20336 cpu_usage 55
pid 20336 cpu_usage 55
pid 20336 cpu_usage 55
pid 20336 cpu_usage 55
pid 20336 cpu_usage 57
pid 20336 cpu_usage 53
cpuctl_test_fj 1 TPASS : case21 PASS
-------------------
Signed-off-by: Shi Weihua <shiwh@cn.fujitsu.com>
---
--- ltp-full-20091231/testcases/kernel/controllers/cpuctl_fj/run_cpuctl_test_fj.sh 2009-11-16 15:40:40.000000000 +0800
+++ ltp-full-20091231.new/testcases/kernel/controllers/cpuctl_fj/run_cpuctl_test_fj.sh 2010-01-06 12:36:32.000000000 +0800
@@ -85,7 +85,10 @@ creat_process()
get_cpu_usage()
{
- ps -eo 'pid,pcpu' | awk '$1 == "'$1'" { sub(/(\.[[:digit:]])*$/, "", $2); print $2 }'
+ top=($(top -b -n 1 -p $1 | tail -2 | head -1))
+ top=${top[8]}
+ top=`echo $top | awk -F "." '{print $1}'`
+ echo "$top"
}
kill_all_pid()
@@ -627,7 +630,7 @@ case21()
do
cpu_usage=$(get_cpu_usage $pid)
echo "pid $pid cpu_usage $cpu_usage"
- expr 44 \< "$cpu_usage" \& "$cpu_usage" \< 56 > /dev/null 2>&1
+ expr 40 \< "$cpu_usage" \& "$cpu_usage" \< 60 > /dev/null 2>&1
ret=$?
: $(( top_times+=1 ))
done
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-01-06 4:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 4:58 Shi Weihua [this message]
2010-01-06 5:24 ` [LTP] [PATCH] cpuctl_fj: replace ps by top to fix cpu usage's computation error Garrett Cooper
2010-01-06 9:47 ` Shi Weihua
2010-01-20 0:30 ` Jiri Palecek
2010-01-20 2:52 ` Garrett Cooper
2010-01-22 11:25 ` Jiří Paleček
2010-01-23 22:38 ` Garrett Cooper
2010-01-23 22:38 ` Garrett Cooper
2010-01-24 0:22 ` Jiří Paleček
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=4B44187D.5030702@cn.fujitsu.com \
--to=shiwh@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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