From: Shizhao Chen <shichen@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] numa01.sh: unset default cpuset awareness before verify physcpubind
Date: Fri, 15 Sep 2023 14:04:25 +0800 [thread overview]
Message-ID: <20230915060425.47337-1-shichen@redhat.com> (raw)
On systems with cpu isolation configured (a very common technique used in the
real time kernel), $run_on_cpu may happen to be an isolated core and hence
unaccessible to numactl.
Unset default cpuset awareness with --all, so numactl can use all possible
CPUs/nodes for following physcpubind settings.
Signed-off-by: Shizhao Chen <shichen@redhat.com>
Reviewed-by: Li Wang <liwang@redhat.com>
---
testcases/kernel/numa/numa01.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testcases/kernel/numa/numa01.sh b/testcases/kernel/numa/numa01.sh
index 367813ce9..0181cd8f5 100755
--- a/testcases/kernel/numa/numa01.sh
+++ b/testcases/kernel/numa/numa01.sh
@@ -183,7 +183,7 @@ test4()
no_of_cpus=$(tst_ncpus)
# not sure whether cpu's can't be in odd number
run_on_cpu=$(($((no_of_cpus+1))/2))
- numactl --physcpubind=$run_on_cpu support_numa pause & #just waits for sigint
+ numactl --all --physcpubind=$run_on_cpu support_numa pause & #just waits for sigint
pid=$!
var=`awk '{ print $2 }' /proc/$pid/stat`
while [ $var = '(numactl)' ]; do
--
2.41.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2023-09-15 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 6:04 Shizhao Chen [this message]
2023-09-15 7:56 ` [LTP] [PATCH] numa01.sh: unset default cpuset awareness before verify physcpubind Li Wang
-- strict thread matches above, loose matches on Subject: below --
2023-09-11 11:22 Shizhao Chen
2023-09-12 8:31 ` 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=20230915060425.47337-1-shichen@redhat.com \
--to=shichen@redhat.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