From: Andi Kleen <andi@firstfloor.org>
To: Jon Stanley <jonstanley@gmail.com>
Cc: linux-numa@vger.kernel.org, pholasek@redhat.com
Subject: Re: numactl using it's own affinity to determine CPU set
Date: Mon, 22 Oct 2012 21:41:41 +0200 [thread overview]
Message-ID: <20121022194141.GT16230@one.firstfloor.org> (raw)
In-Reply-To: <CALY6xnjEHtoTjiPU=jTDSppKkYdCqZMC-tnNYYf54zbMzhZeTQ@mail.gmail.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
> <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
next prev parent reply other threads:[~2012-10-22 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 19:35 numactl using it's own affinity to determine CPU set Jon Stanley
2012-10-22 19:41 ` Andi Kleen [this message]
2012-10-22 20:12 ` Jon Stanley
2012-10-23 12:21 ` Petr Holasek
2012-10-23 14:19 ` Cliff Wickman
2012-10-23 21:17 ` Petr Holasek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121022194141.GT16230@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jonstanley@gmail.com \
--cc=linux-numa@vger.kernel.org \
--cc=pholasek@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).