From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH] sched: Fix numabalancing to work with isolated cpus
Date: Thu, 6 Apr 2017 12:47:57 +0200 [thread overview]
Message-ID: <20170406104757.kemq6is6nh6f26fx@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170406104204.GI5497@dhcp22.suse.cz>
On Thu, Apr 06, 2017 at 12:42:04PM +0200, Michal Hocko wrote:
> Is this something dictated by usecases which rely on isolcpus or rather
> nobody bothered to implement one scheduling domain?
Its from the original use-case I suspect. It was done very much on
purpose.
If you want bigger partitions use cpusets. Or rather, like I've been
saying for many years, use cpusets for everything and kill isolcpus.
Problem with that last part is cgroups.. you then need to make a !root
cgroup the 'default' cgroup in order to represent that.
I really should've done this before all that cgroup crap came along, too
late now :/
next prev parent reply other threads:[~2017-04-06 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 17:27 Srikar Dronamraju
2017-04-04 18:56 ` Rik van Riel
2017-04-04 20:37 ` Mel Gorman
2017-04-05 1:50 ` Srikar Dronamraju
2017-04-05 8:09 ` Mel Gorman
2017-04-05 12:57 ` Michal Hocko
2017-04-05 15:22 ` Srikar Dronamraju
2017-04-05 16:44 ` Michal Hocko
2017-04-06 7:19 ` Srikar Dronamraju
2017-04-06 7:34 ` Michal Hocko
2017-04-06 9:23 ` Peter Zijlstra
2017-04-06 10:13 ` Michal Hocko
2017-04-06 10:29 ` Peter Zijlstra
2017-04-06 10:42 ` Michal Hocko
2017-04-06 10:47 ` Peter Zijlstra [this message]
2017-04-06 13:44 ` Michal Hocko
2017-04-06 7:36 ` Mike Galbraith
2017-04-06 7:36 ` Peter Zijlstra
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=20170406104757.kemq6is6nh6f26fx@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
--subject='Re: [PATCH] sched: Fix numabalancing to work with isolated cpus' \
/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
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.