All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: qiuxishi@huawei.com, guohanjun@huawei.com
Subject: is it a problem when cat /proc/pid/status
Date: Mon, 31 Aug 2015 15:33:42 +0800	[thread overview]
Message-ID: <55E40356.3050800@huawei.com> (raw)


I want to know whether the NUMA bound memory node with CONFIG_CGROUPS related or associted with NUMA binding.

I wrote an example test,the results are as follows.

> euler-linux:/home/zhongjiang # numactl --membind=1 ./new &
> [1] 6529
> euler-linux:/home/zhongjiang # ps -ef | grep new
> root      6529  4483  0 14:40 pts/1    00:00:00 ./new
> root      6556  4483  0 14:40 pts/1    00:00:00 grep new
> euler-linux:/home/zhongjiang # cat /proc/6529/status
> Name:   new
> State:  S (sleeping)
  ........
> Cpus_allowed:   ffffff
> Cpus_allowed_list:      0-23
> Mems_allowed:   00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,007fffff
> Mems_allowed_list:      0-22
> voluntary_ctxt_switches:        19
> nonvoluntary_ctxt_switches:     0


euler-linux:/home/zhongjiang # numactl --membind=3 ./new &
[1] 9113
euler-linux:/home/zhongjiang # ps -ef | grep mew
root      9140  8948  0 14:55 pts/1    00:00:00 grep mew
euler-linux:/home/zhongjiang # ps -ef | grep new
root      9113  8948  0 14:55 pts/1    00:00:00 ./new
root      9209  8948  0 14:55 pts/1    00:00:00 grep new
euler-linux:/home/zhongjiang # cat /proc/9113/status
Name:   new
State:  S (sleeping)
Tgid:   9113
Ngid:   0
Pid:    9113
PPid:   8948
......
Cpus_allowed:   ffffff
Cpus_allowed_list:      0-23
Mems_allowed:   00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,007fffff
Mems_allowed_list:      0-22
voluntary_ctxt_switches:        26
nonvoluntary_ctxt_switches:     0

Through the comparison of the above, I can find Whatever I use node for binding, the mems_allowed fields has been no change

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: zhong jiang <zhongjiang@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <qiuxishi@huawei.com>, <guohanjun@huawei.com>
Subject: is it a problem when cat /proc/pid/status
Date: Mon, 31 Aug 2015 15:33:42 +0800	[thread overview]
Message-ID: <55E40356.3050800@huawei.com> (raw)


I want to know whether the NUMA bound memory node with CONFIG_CGROUPS related or associted with NUMA binding.

I wrote an example test,the results are as follows.

> euler-linux:/home/zhongjiang # numactl --membind=1 ./new &
> [1] 6529
> euler-linux:/home/zhongjiang # ps -ef | grep new
> root      6529  4483  0 14:40 pts/1    00:00:00 ./new
> root      6556  4483  0 14:40 pts/1    00:00:00 grep new
> euler-linux:/home/zhongjiang # cat /proc/6529/status
> Name:   new
> State:  S (sleeping)
  ........
> Cpus_allowed:   ffffff
> Cpus_allowed_list:      0-23
> Mems_allowed:   00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,007fffff
> Mems_allowed_list:      0-22
> voluntary_ctxt_switches:        19
> nonvoluntary_ctxt_switches:     0


euler-linux:/home/zhongjiang # numactl --membind=3 ./new &
[1] 9113
euler-linux:/home/zhongjiang # ps -ef | grep mew
root      9140  8948  0 14:55 pts/1    00:00:00 grep mew
euler-linux:/home/zhongjiang # ps -ef | grep new
root      9113  8948  0 14:55 pts/1    00:00:00 ./new
root      9209  8948  0 14:55 pts/1    00:00:00 grep new
euler-linux:/home/zhongjiang # cat /proc/9113/status
Name:   new
State:  S (sleeping)
Tgid:   9113
Ngid:   0
Pid:    9113
PPid:   8948
......
Cpus_allowed:   ffffff
Cpus_allowed_list:      0-23
Mems_allowed:   00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,007fffff
Mems_allowed_list:      0-22
voluntary_ctxt_switches:        26
nonvoluntary_ctxt_switches:     0

Through the comparison of the above, I can find Whatever I use node for binding, the mems_allowed fields has been no change


             reply	other threads:[~2015-08-31  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  7:33 zhong jiang [this message]
2015-08-31  7:33 ` is it a problem when cat /proc/pid/status zhong jiang

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=55E40356.3050800@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=qiuxishi@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.