[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1520868085.9178.1.camel@gmx.de>
Date: Mon, 12 Mar 2018 16:21:25 +0100
From: Mike Galbraith <efault@....de>
To: Waiman Long <longman@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Cc: Tejun Heo <tj@...nel.org>, Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Ingo Molnar <mingo@...hat.com>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
kernel-team@...com, pjt@...gle.com, luto@...capital.net,
torvalds@...ux-foundation.org, Roman Gushchin <guro@...com>
Subject: Re: [PATCH v4] cpuset: Enable cpuset controller in default hierarchy
On Mon, 2018-03-12 at 10:20 -0400, Waiman Long wrote:
> On 03/10/2018 08:16 AM, Peter Zijlstra wrote:
>
> > The equivalent of isolcpus=xxx is a cgroup setup like:
> >
> > root
> > / \
> > system other
> >
> > Where other has the @xxx cpus and system the remainder and
> > root.sched_load_balance = 0.
>
> I saw in the kernel-parameters.txt file that the isolcpus option was
> deprecated - use cpusets instead. However, there doesn't seem to have
> document on the right way to do it.
I use cset shield (cpuset package) in a script to create a set and
migrate everything that's permitted into the system set.
setup:
cset shield --userset=rtcpus --cpu=4-63 --kthread=on
<poke this/that>
teardown:
cset shield --userset=rtcpus --reset
<un-poke this/that>
Non-sexy, but works for simple stuff.
-Mike
Powered by blists - more mailing lists