From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: A question about numa_set_membind()
Date: Sun, 3 Jun 2012 20:31:46 +0200
Message-ID: <20120603183146.GE27374@one.firstfloor.org>
References: <CADbtAaKGc_N7xegjDixMiGJK85p0_Hm-O8yYvEA+4QkYQO0uDQ@mail.gmail.com>
Mime-Version: 1.0
Return-path: <linux-numa-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <CADbtAaKGc_N7xegjDixMiGJK85p0_Hm-O8yYvEA+4QkYQO0uDQ@mail.gmail.com>
Sender: linux-numa-owner@vger.kernel.org
List-ID: <linux-numa.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Wei Chen <acee06.weichen@gmail.com>
Cc: linux-numa@vger.kernel.org

On Sun, Jun 03, 2012 at 12:45:07PM +0900, Wei Chen wrote:
> Dear all,
> 
> Recently I am confused about numa_set_membind() for global arrays. If
> we have a global array and later we call numa_set_membind() in our
> code, will that global array be set to the node specified by the
> nodemask_t. As I know, global array is allocated in the global data
> area by the compiler before program executes. So I wonder whether
> numa_set_membind() affects global variables and how. Besides, I would
> like to know if there is one global data area for each node or all
> memory only share one global data area. If all memory only share one
> global data area, how to decide the distance between each node and the
> global data area?


The memory of the global array is only faulted in at first touch.
That is when the memory policy takes affect.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.