From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: numactl problems with -C option specifying cpus outside of
 cpus_allowed
Date: Wed, 2 Oct 2013 21:01:49 +0200
Message-ID: <20131002190149.GA6882@two.firstfloor.org>
References: <00000141799702db-dbec8157-ae1f-43b6-8a30-ec1653be5d31-000000@email.amazonses.com>
Mime-Version: 1.0
Return-path: <linux-numa-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <00000141799702db-dbec8157-ae1f-43b6-8a30-ec1653be5d31-000000@email.amazonses.com>
Sender: linux-numa-owner@vger.kernel.org
List-ID: <linux-numa.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Christoph Lameter <cl@linux.com>
Cc: pholasek@redhat.com, linux-numa@vger.kernel.org

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?

Copying linux-numa and Petr.

-Andi


-- 
ak@linux.intel.com -- Speaking for myself only.