From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751565AbdJ0N6u (ORCPT <rfc822;w@1wt.eu>);
        Fri, 27 Oct 2017 09:58:50 -0400
Received: from bombadil.infradead.org ([65.50.211.133]:51979 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750781AbdJ0N6r (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 27 Oct 2017 09:58:47 -0400
Date: Fri, 27 Oct 2017 15:58:31 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: cmetcalf@mellanox.com, linux-kernel@vger.kernel.org,
        tglx@linutronix.de, torvalds@linux-foundation.org, hpa@zytor.com,
        riel@redhat.com, cl@linux.com, mingo@kernel.org, efault@gmx.de,
        frederic@kernel.org, kernellwp@gmail.com, paulmck@linux.vnet.ibm.com,
        lcapitulino@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags
Message-ID: <20171027135831.GZ3165@worktop.lehotels.local>
References: <1509072159-31808-13-git-send-email-frederic@kernel.org>
 <tip-98a06af93784a6ae541e9fc6292ef26177832543@git.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <tip-98a06af93784a6ae541e9fc6292ef26177832543@git.kernel.org>
User-Agent: Mutt/1.5.22.1 (2013-10-16)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Oct 27, 2017 at 05:06:25AM -0700, tip-bot for Frederic Weisbecker wrote:
> +	isolcpus=	[KNL,SMP] Isolate a given set of CPUs from disturbance.
> +			Format: [flag-list,]<cpu-list>
> +
> +			Specify one or more CPUs to isolate from disturbances
> +			specified in the flag list (default: domain):
> +
> +			nohz
> +			  Disable the tick when a single task runs.
> +			domain
> +			  Isolate from the general SMP balancing and scheduling
> +			  algorithms. This option is the preferred way to isolate
> +			  CPUs from tasks. 

I _strongly_ object to this statement, isolcpus is _not_ the preferred
way, cpusets are.

And yes, while cpusets suffers some problems, we _should_ really fix
those and not promote this piece of shit isolcpus crap.

> The alternative -- manually setting the
> +			  CPU mask of all tasks in the system, can cause problems
> +			  and suboptimal load balancer performance. You can move a
> +			  process onto or off an "isolated" CPU via the CPU
> +			  affinity syscalls or cpuset. <cpu number> begins at 0
> +			  and the maximum value is "number of CPUs in system - 1".
> +
> +			The format of <cpu-list> is described above.
> +