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 > <see directory goodness> > $ taskset -p f $$ > $ numactl --physcpubind=5 ls > libnuma: Warning: cpu argument 5 is out of range > <snip> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-numa" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
