[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <55D6EEEB.7050701@huawei.com>
Date: Fri, 21 Aug 2015 17:27:07 +0800
From: Xishi Qiu <qiuxishi@...wei.com>
To: LKML <linux-kernel@...r.kernel.org>, Linux MM <linux-mm@...ck.org>
CC: Xishi Qiu <qiuxishi@...wei.com>, Xiexiuqi <xiexiuqi@...wei.com>
Subject: is this a problem of numactl in RedHat7.0 ?
I use numactl(--localalloc) tool run a test case, but it shows that
the numa policy is prefer, I don't know why.
[root@...alhost test]# numactl --hard
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 12 13 14 15 16 17
node 0 size: 32739 MB
node 0 free: 29134 MB
node 1 cpus: 6 7 8 9 10 11 18 19 20 21 22 23
node 1 size: 32768 MB
node 1 free: 31682 MB
node distances:
node 0 1
0: 10 20
1: 20 10
[root@...alhost test]# numactl --localalloc --physcpubind=22 ./test.exe
[root@...alhost linux-3.10-redhat]# ps -ef| grep test
root 18532 13994 1 05:24 pts/0 00:00:00 ./test.exe
root 18534 14037 0 05:24 pts/1 00:00:00 grep --color=auto test
[root@...alhost linux-3.10-redhat]# cat /proc/18532/numa_maps
00400000 prefer:0 file=/home/qiuxishi/test/test.exe mapped=1 N0=1
00600000 prefer:0 file=/home/qiuxishi/test/test.exe anon=1 dirty=1 N1=1
00601000 prefer:0 file=/home/qiuxishi/test/test.exe anon=1 dirty=1 N1=1
7f1a15b9b000 prefer:0 file=/usr/lib64/libc-2.17.so mapped=51 mapmax=44 N0=49 N1=2
7f1a15d51000 prefer:0 file=/usr/lib64/libc-2.17.so
7f1a15f51000 prefer:0 file=/usr/lib64/libc-2.17.so anon=4 dirty=4 N1=4
7f1a15f55000 prefer:0 file=/usr/lib64/libc-2.17.so anon=2 dirty=2 N1=2
7f1a15f57000 prefer:0 anon=3 dirty=3 N1=3
7f1a15f5c000 prefer:0 file=/usr/lib64/ld-2.17.so mapped=28 mapmax=15 N0=23 N1=5
7f1a16166000 prefer:0 anon=3 dirty=3 N1=3
7f1a1617c000 prefer:0 anon=1 dirty=1 N1=1
7f1a1617d000 prefer:0 file=/usr/lib64/ld-2.17.so anon=1 dirty=1 N1=1
7f1a1617e000 prefer:0 file=/usr/lib64/ld-2.17.so anon=1 dirty=1 N1=1
7f1a1617f000 prefer:0 anon=1 dirty=1 N1=1
7ffd0d2ed000 prefer:0 stack anon=3 dirty=3 N1=3
7ffd0d3fc000 prefer:0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists