From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752844AbbHaHue (ORCPT <rfc822;w@1wt.eu>);
	Mon, 31 Aug 2015 03:50:34 -0400
Received: from lhrrgout.huawei.com ([194.213.3.17]:61377 "EHLO
	lhrrgout.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752646AbbHaHud (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 31 Aug 2015 03:50:33 -0400
Message-ID: <55E40356.3050800@huawei.com>
Date: Mon, 31 Aug 2015 15:33:42 +0800
From: zhong jiang <zhongjiang@huawei.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
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
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.177.29.68]
X-CFilter-Loop: Reflected
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


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