From: Petr Holasek <pholasek@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-numa@vger.kernel.org
Subject: Re: numactl problems with -C option specifying cpus outside of cpus_allowed
Date: Thu, 3 Oct 2013 17:56:06 +0200 [thread overview]
Message-ID: <20131003155606.GA30005@thinkpad-work.redhat.com> (raw)
In-Reply-To: <000001417e93dd7e-d18881f0-6ad9-4f67-bcef-89842502d68c-000000@email.amazonses.com>
On Thu, 03 Oct 2013, Christoph Lameter wrote:
> On Wed, 2 Oct 2013, Andi Kleen wrote:
>
> > On Wed, Oct 02, 2013 at 02:34:01PM +0000, Christoph Lameter wrote:
> > > It seems that the check for processors specified with C is always done
> > > regardless of CAP_SYS_NICE or the possibility that root may be calling
> > > numactl.
> > >
> > > taskset does not have that problem. Nor did releases of numactl before
> > > 2.0.8.
> >
> > The recently added --all option may help?
>
> Which version added --all? Would the correct approach not be to check if
> its root runninng numactl or if CAP_SYS_NICE is set?
--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.
next prev parent reply other threads:[~2013-10-03 15:56 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 [this message]
2013-10-03 17:37 ` Christoph Lameter
2013-10-03 22:33 ` Andi Kleen
2013-10-03 22:46 ` 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=20131003155606.GA30005@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 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.