From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: numactl using it's own affinity to determine CPU set Date: Mon, 22 Oct 2012 21:41:41 +0200 Message-ID: <20121022194141.GT16230@one.firstfloor.org> References: Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-numa-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jon Stanley Cc: linux-numa@vger.kernel.org, pholasek@redhat.com On Mon, Oct 22, 2012 at 03:35:42PM -0400, Jon Stanley wrote: > If you set the affinity of your shell to be a subset of the available > CPUs, and then attempt to use numactl to bind to something that is not > in that affinity mask, the attempt will fail. I thought that this was > fixed in the current numactl 2.0.8, but it doesn't seem to be. > > A simple reproducer on a 2-node 8-core system is as such: > > $ numactl --physcpubind=5 ls > > $ taskset -p f $$ > $ numactl --physcpubind=5 ls > libnuma: Warning: cpu argument 5 is out of range > That was done intentional at some point to handle cpusets. numactl 1.0 or so didn't have that problem. However it's unclear if it's really bug. Presumably could have an option to override. -Andi