From: Mike Galbraith <efault@gmx.de>
To: Waiman Long <longman@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Ingo Molnar <mingo@redhat.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, kernel-team@fb.com, pjt@google.com,
luto@amacapital.net, torvalds@linux-foundation.org,
Roman Gushchin <guro@fb.com>
Subject: Re: [PATCH v4] cpuset: Enable cpuset controller in default hierarchy
Date: Mon, 12 Mar 2018 16:21:25 +0100 [thread overview]
Message-ID: <1520868085.9178.1.camel@gmx.de> (raw)
In-Reply-To: <12ef7f60-5b14-8e09-2478-1453a3071f21@redhat.com>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-03-12 15:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 15:35 [PATCH v4] cpuset: Enable cpuset controller in default hierarchy Waiman Long
2018-03-09 16:34 ` Mike Galbraith
2018-03-09 17:23 ` Mike Galbraith
2018-03-09 17:45 ` Waiman Long
2018-03-09 18:17 ` Mike Galbraith
2018-03-09 18:20 ` Waiman Long
2018-03-09 19:40 ` Mike Galbraith
2018-03-09 20:43 ` Waiman Long
2018-03-09 22:17 ` Peter Zijlstra
2018-03-09 23:06 ` Waiman Long
2018-03-10 3:47 ` Mike Galbraith
2018-03-14 19:57 ` Tejun Heo
2018-03-15 2:49 ` Mike Galbraith
2018-03-19 15:34 ` Tejun Heo
2018-03-19 20:49 ` Mike Galbraith
2018-03-19 21:41 ` Waiman Long
2018-03-20 4:25 ` Mike Galbraith
2018-03-10 13:16 ` Peter Zijlstra
2018-03-12 14:20 ` Waiman Long
2018-03-12 15:21 ` Mike Galbraith [this message]
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=1520868085.9178.1.camel@gmx.de \
--to=efault@gmx.de \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).