From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 3/3] ltp/numa: use string to describe operation
Date: Tue, 23 May 2017 14:15:15 +0200 [thread overview]
Message-ID: <20170523121515.GC19602@rei.suse.cz> (raw)
In-Reply-To: <CAEemH2c2zzixjetBj8hKCgD_2tCiSN9FrE=0aNUmo4P9vDwD2A@mail.gmail.com>
Hi!
> $ git diff
> diff --git a/testcases/kernel/numa/numa01.sh b/testcases/kernel/numa/numa01.sh
> index 4eda3f1..e3fe854 100755
> --- a/testcases/kernel/numa/numa01.sh
> +++ b/testcases/kernel/numa/numa01.sh
> @@ -315,9 +315,20 @@ test8()
> # Memory will be allocated using round robin on nodes.
> Exp_incr=$(echo "$MB / $total_nodes" |bc)
>
> - numactl --interleave=all memhog -r1000000 1MB 2>&1 >/dev/null &
> + numactl --interleave=all memhog -r1000000 1MB 2>&1 >ltp_numa_test8.log &
> pid=$!
>
> + local retries=20
> + while [ $retries -gt 0 ]; do
> +
> + if grep -m1 -q '.' ltp_numa_test8.log; then
> + break
> + fi
> +
> + retries=$((retries-1))
> + tst_sleep 50ms
> + done
> +
> for node in $nodes_list; do
> Mem_curr=$(echo "$(extract_numastat_p $pid $node) * $MB" |bc)
This fixes the problem for me, can you, pretty please, send a signed
patch?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-05-23 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 8:27 [LTP] [PATCH v3 3/3] ltp/numa: use string to describe operation Li Wang
2017-05-19 12:23 ` Cyril Hrubis
2017-05-22 3:54 ` Li Wang
2017-05-23 12:15 ` Cyril Hrubis [this message]
2017-05-24 1:48 ` Li Wang
-- strict thread matches above, loose matches on Subject: below --
2017-05-19 8:25 [LTP] [PATCH v3 1/3] ltp/numa: add new test11 Li Wang
2017-05-19 8:25 ` [LTP] [PATCH v3 3/3] ltp/numa: use string to describe operation Li Wang
2017-05-19 8:32 ` 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=20170523121515.GC19602@rei.suse.cz \
--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