From: Harish <harish@linux.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] numa01.sh: Fix parsing numastat for given node
Date: Thu, 2 Jul 2020 15:20:29 +0530 [thread overview]
Message-ID: <20200702095029.35220-1-harish@linux.ibm.com> (raw)
In few systems, the node numbering is not necessarily ordered.
E.g.
Per-node process memory usage (in MBs) for PID 2069 (systemd-udevd)
Node 0 Node 8 Total
--------------- --------------- ---------------
...
...
---------------- --------------- --------------- ---------------
Total 17.50 0.00 17.50
Patch fixes parsing numastat for given node by finding its awk
index so that proper value is utilized in the test.
Signed-off-by: Harish <harish@linux.ibm.com>
---
testcases/kernel/numa/numa01.sh | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/testcases/kernel/numa/numa01.sh b/testcases/kernel/numa/numa01.sh
index 1d626327d..fd437cd15 100755
--- a/testcases/kernel/numa/numa01.sh
+++ b/testcases/kernel/numa/numa01.sh
@@ -25,15 +25,26 @@ TST_NEEDS_CMDS="awk bc numactl numastat"
. tst_test.sh
+# Awk the field matching the node value for numastat
+# $1 - Pid number
+# $2 - Node number
+get_node_index()
+{
+ local pid=$1
+ local nid="Node $2"
+ echo $(numastat -p $pid | sed '3q;d' | awk -F '[[:space:]][[:space:]]+' \
+ -v node="$nid" '{ for (i = 1; i <= NF; ++i) if($i==node) print i; exit }')
+}
+
# Extracts the value of given numa node from the `numastat -p` output.
# $1 - Pid number.
# $2 - Node number.
extract_numastat_p()
{
local pid=$1
- local node=$(($2 + 2))
+ local index=$(echo "$(get_node_index $pid $2)")
- echo $(numastat -p $pid |awk '/^Total/ {print $'$node'}')
+ echo $(numastat -p $pid |awk '/^Total/ {print $'$index'}')
}
check_for_support_numa()
@@ -341,8 +352,8 @@ test9()
numactl --cpunodebind=$node --membind=$node support_numa alloc_1huge_page &
pid=$!
TST_RETRY_FUNC "check_for_support_numa $pid" 0
-
- Mem_huge=$(echo $(numastat -p $pid |awk '/^Huge/ {print $'$((node+2))'}'))
+ local index=$(echo "$(get_node_index $pid $node)")
+ Mem_huge=$(echo $(numastat -p $pid |awk '/^Huge/ {print $'$index'}'))
Mem_huge=$((${Mem_huge%.*} * 1024))
if [ "$Mem_huge" -lt "$HPAGE_SIZE" ]; then
--
2.25.4
next reply other threads:[~2020-07-02 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 9:50 Harish [this message]
2020-07-02 10:08 ` [LTP] [PATCH] numa01.sh: Fix parsing numastat for given node 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=20200702095029.35220-1-harish@linux.ibm.com \
--to=harish@linux.ibm.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