From: Petr Holasek <pholasek@redhat.com>
To: Jon Stanley <jonstanley@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-numa@vger.kernel.org, Cliff Wickman <cpw@sgi.com>
Subject: Re: numactl using it's own affinity to determine CPU set
Date: Tue, 23 Oct 2012 14:21:40 +0200 [thread overview]
Message-ID: <20121023122139.GA5766@machinehead.brq.redhat.com> (raw)
In-Reply-To: <CALY6xnigpTnSM0rm9QZO4E7OZ-Qz0Wi0hi+61GpvFGU2NkB8Lg@mail.gmail.com>
Hi everyone,
On Mon, 22 Oct 2012, Jon Stanley wrote:
> On Mon, Oct 22, 2012 at 3:41 PM, Andi Kleen <andi@firstfloor.org> wrote:
> > That was done intentional at some point to handle cpusets.
> > numactl 1.0 or so didn't have that problem.
>
> I'll happily admit to not being an expert here :)
I've added new interface for parsing cpusets/nodesets with _all() suffix
in 2.0.8-rc5 libnuma, but numactl utility still uses old ones with cpuset
awareness. I didn't want to dig into some libnuma internals and change
behaviour of dependent utils in such way.
>
> However, I thought that the concept of cpusets was that if you
> attempted to set affinity outside of your cpuset, that would silently
> fail. I assume that the reason that libnuma didn't want to set outside
> of it's own affinity mask is to avoid such a silent failure?
>
> Also, I question the Real World(TM) prevalence of cpusets.
>
> > However it's unclear if it's really bug.
>
> Not sure if I'd call it a bug since it was intentional, but sure would
> call it an unexpected change in behavior :)
I like the idea of some overriding option proposed by Andi.
btw, Cliff, can you remember what was the reason for this change in some
version after 1.0?
Petr
next prev parent reply other threads:[~2012-10-23 12:21 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
2012-10-22 20:12 ` Jon Stanley
2012-10-23 12:21 ` Petr Holasek [this message]
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=20121023122139.GA5766@machinehead.brq.redhat.com \
--to=pholasek@redhat.com \
--cc=andi@firstfloor.org \
--cc=cpw@sgi.com \
--cc=jonstanley@gmail.com \
--cc=linux-numa@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.