From: Michal Hocko <mhocko@kernel.org>
To: Peter Zijlstra <peterz@infradead.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:13:49 +0200 [thread overview]
Message-ID: <20170406101348.GH5497@dhcp22.suse.cz> (raw)
In-Reply-To: <20170406092329.52zzkxlkvitnh44c@hirez.programming.kicks-ass.net>
On Thu 06-04-17 11:23:29, Peter Zijlstra wrote:
> On Thu, Apr 06, 2017 at 09:34:36AM +0200, Michal Hocko wrote:
[...]
> > I would really like to see it confirmed by the scheduler maintainers and
> > documented properly as well. What you are claiming here is rather
> > surprising to my understanding of what isolcpus acutally is.
>
> isolcpus gets you a set of fully partitioned CPUs. What's surprising
> about that?
Well, I thought that all isolated cpus simply form their own scheduling
domain which is isolated from the general workload on the system
(kthreads, softirqs etc...).
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-04-06 10:14 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 [this message]
2017-04-06 10:29 ` Peter Zijlstra
2017-04-06 10:42 ` Michal Hocko
2017-04-06 10:47 ` Peter Zijlstra
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=20170406101348.GH5497@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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.