From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752647AbdJ0Oj6 (ORCPT ); Fri, 27 Oct 2017 10:39:58 -0400 Received: from mout.gmx.net ([212.227.15.15]:60662 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751942AbdJ0Oju (ORCPT ); Fri, 27 Oct 2017 10:39:50 -0400 Message-ID: <1509115109.6780.8.camel@gmx.de> Subject: Re: [tip:sched/core] sched/isolation: Document the isolcpus= flags From: Mike Galbraith To: Peter Zijlstra , 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, frederic@kernel.org, kernellwp@gmail.com, paulmck@linux.vnet.ibm.com, lcapitulino@redhat.com Cc: linux-tip-commits@vger.kernel.org Date: Fri, 27 Oct 2017 16:38:29 +0200 In-Reply-To: <20171027135831.GZ3165@worktop.lehotels.local> References: <1509072159-31808-13-git-send-email-frederic@kernel.org> <20171027135831.GZ3165@worktop.lehotels.local> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:dGOcYsyJHFRQ21K9gNSAsSo805Lud01mKMUhV4+X+4voI8PrZbW 79KAcyzhz32mXwQcKkdrprDYVYjt5Q8FC/YxpreNf8UFrDav1yO/JgfO/ZSIH37e8Z0SnO2 v5Z87id0s8a4pZfHcrAjH4hcdk7n0GiT4Ihap6xCiGoG7HRh27LCGB+spoU9XkX1mCbDtgi IE+NOVPFFd1aoLxxKOWKQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:IKJbK1wPr+4=:kZTUq2yegzx/NR+R3mEVWy i9tp4DWV7ZTNPQRJ1FNqekh1bGOkr5r4rkOAmVFqSn7aRsw9DF+tSc381Ulw6YkM76ipThdyd 1F4OBKqWWsn+iyCamSbT/zbC6hFO7F30/EC7TTZwE4xmuNduGtGLy3ASIUT3kWAt/GyHGh5XZ XzW/N1SFK6f6m0t207UlWe/WfGTi5t7SytJiH3rKDzrE/Y37NYzqCdXqHtGtm6s8g+gBFu9ln rMQOs6jJ9wfyQiLdP1ztxaM9JI6wYlrU/hOW6KADIq2gPBfA9UZy3laNitby7ornYRwpxaiUv IiCSdU3UPUdpmHAfnCWGCN5AKsje5SGNgDztIVGuseaWKhyzfgKOHYCh6S6j4IksY/leL3Gld XrLil/LSH20xCF0d4CD4feYLBC84FFKqA08TK3mCv8rfzpsJVu56aZFNKatiGtWESFmuuyUUW tfIMm9QsFrbQl2i9gxihMP1kFPtCc28/7+dUqaf7w+v4IIqvmI2CctCFcK6ENhlDLk3xWHHPe 7eFPy6cALOMtHmAnsGScN7SIhXGKCUlLzhz8mRr7o1GM2z3yBMHwSJn+swHj4qMSSFa5Vqh7w 5KDECTJtweeaIVReZ8zACQpliYqycME+ebCeEnUYD3Uq2Wz/dXYRmTWuKzS+jskuHq0AJ/pGs 9XXqyeZpXQyRIKeKVcpWp66KTZ7uZyVpymdVdw5HB0031ewsJBpBbgcQ17H1DPspnGQMH4gu1 7r6FIIKWXwzEHOHXwRtyz3IEffxDkD9mGNODsopjqVEn48L+3jbRfuKArb/0uu+L2PIRLDSTp 2axzcA4fHWuP+eKWq2kRHkZmm7wmtlF53vWz5W5LDImm+x1XPQ= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2017-10-27 at 15:58 +0200, Peter Zijlstra wrote: > 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,] > > + > > + 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. +1, isolcpus is the dinosaur that just won't frickn' die. -Mike