From: Petr Holasek <pholasek@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Christoph Lameter <cl@linux.com>, linux-numa@vger.kernel.org
Subject: Re: numactl problems with -C option specifying cpus outside of cpus_allowed
Date: Fri, 4 Oct 2013 00:46:01 +0200 [thread overview]
Message-ID: <20131003224601.GB30005@thinkpad-work.redhat.com> (raw)
In-Reply-To: <20131003223339.GC6882@two.firstfloor.org>
On Fri, 04 Oct 2013, Andi Kleen wrote:
> > > --all option was added in version 2.0.9-rc5. When CAP_SYS_NICE is not set,
> > > numactl will fail in sched_setaffinity() call even so.
> >
> > numactl should allow the setting of affinities if CAP_SYS_NICE is set.
>
> It does if you pass --all, correct?
>
> -Andi
>
Yes, you're right.
prev parent reply other threads:[~2013-10-03 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000141799702db-dbec8157-ae1f-43b6-8a30-ec1653be5d31-000000@email.amazonses.com>
2013-10-02 19:01 ` numactl problems with -C option specifying cpus outside of cpus_allowed Andi Kleen
2013-10-03 13:48 ` Christoph Lameter
2013-10-03 15:56 ` Petr Holasek
2013-10-03 17:37 ` Christoph Lameter
2013-10-03 22:33 ` Andi Kleen
2013-10-03 22:46 ` Petr Holasek [this message]
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=20131003224601.GB30005@thinkpad-work.redhat.com \
--to=pholasek@redhat.com \
--cc=andi@firstfloor.org \
--cc=cl@linux.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 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).