From mboxrd@z Thu Jan  1 00:00:00 1970
From: Petr Holasek <pholasek@redhat.com>
Subject: Re: numactl using it's own affinity to determine CPU set
Date: Tue, 23 Oct 2012 23:17:08 +0200
Message-ID: <20121023211707.GA6827@stainedmachine.redhat.com>
References: <CALY6xnjEHtoTjiPU=jTDSppKkYdCqZMC-tnNYYf54zbMzhZeTQ@mail.gmail.com>
 <20121022194141.GT16230@one.firstfloor.org>
 <CALY6xnigpTnSM0rm9QZO4E7OZ-Qz0Wi0hi+61GpvFGU2NkB8Lg@mail.gmail.com>
 <20121023122139.GA5766@machinehead.brq.redhat.com>
 <20121023141918.GA27082@sgi.com>
Mime-Version: 1.0
Return-path: <linux-numa-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20121023141918.GA27082@sgi.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: Cliff Wickman <cpw@sgi.com>
Cc: Jon Stanley <jonstanley@gmail.com>, Andi Kleen <andi@firstfloor.org>, linux-numa@vger.kernel.org

On Tue, 23 Oct 2012, Cliff Wickman wrote:
> Hi Petr,
> 
> On Tue, Oct 23, 2012 at 02:21:40PM +0200, Petr Holasek wrote:
> > btw, Cliff, can you remember what was the reason for this change in some
> > version after 1.0?
> > 
> > Petr
> 
> Memory nodes allowed was made cpuset-aware by the below patch.
> I'm not quite sure if this is the change you are asking about.
> 
> patch 0804_ls_patch2
> From: Lee Schermerhorn <lee.schermerhorn@hp.com>
> Date: Wed, 02 Apr 2008 14:34:37 -0400
> 
> Depends-on:  MPOL_F_MEMS_ALLOWED kernel patch
> Provide libnuma API for MPOL_F_MEMS_ALLOWED flag.
> Return nodes allowed by the application's current cpuset context
> via new API numa_get_mems_allowed().
> 
> +.BR numa_get_mems_allowed()
> +returns the mask of nodes from which the process is allowed to allocate
> +memory in it's current cpuset context.

Thank you!

I'll check it.

Petr