From: Mike Galbraith <efault@gmx.de>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: RFC [patch] sched,cgroup_sched: convince RT_GROUP_SCHED throttle to work
Date: Wed, 18 Apr 2012 08:27:50 +0200 [thread overview]
Message-ID: <1334730470.5616.33.camel@marge.simpson.net> (raw)
In-Reply-To: <20120418052057.GA19328@zhy>
On Wed, 2012-04-18 at 13:20 +0800, Yong Zhang wrote:
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -5875,6 +5875,11 @@ cpu_attach_domain(struct sched_domain *s
> > sd->child = NULL;
> > }
> >
> > + if (sd)
> > + cpumask_clear_cpu(cpu, cpu_isolated_map);
> > + else
> > + cpumask_set_cpu(cpu, cpu_isolated_map);
> > +
>
> Do we allow this?
Yeah, isolating CPUS 2-3...
[ 3011.444345] CPU0 attaching NULL sched-domain.
[ 3011.448719] CPU1 attaching NULL sched-domain.
[ 3011.453107] CPU2 attaching NULL sched-domain.
[ 3011.457466] CPU3 attaching NULL sched-domain.
[ 3011.461892] CPU0 attaching sched-domain:
[ 3011.465813] domain 0: span 0-1 level MC
[ 3011.469761] groups: 0 1
[ 3011.472415] CPU1 attaching sched-domain:
[ 3011.476333] domain 0: span 0-1 level MC
[ 3011.480266] groups: 1 0
[ 3011.482988] CPU2 attaching sched-domain:
[ 3011.486919] domain 0: span 2-3 level MC
[ 3011.490851] groups: 2 3
[ 3011.493502] CPU3 attaching sched-domain:
[ 3011.497422] domain 0: span 2-3 level MC
[ 3011.501367] groups: 3 2
[ 3011.504214] CPU2 attaching NULL sched-domain.
[ 3011.508569] CPU3 attaching NULL sched-domain.
next prev parent reply other threads:[~2012-04-18 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 9:08 [patch] sched,rt: non-isolated cores lift isolcpus throttle for CONFIG_RT_GROUP_SCHED Mike Galbraith
2012-04-03 9:19 ` [patch] sched,rt: let the user see rt queues in /proc/sched_debug Mike Galbraith
2012-04-07 8:58 ` [patch] sched,cgroup_sched: fix up task_groups list buglet Mike Galbraith
2012-04-07 9:54 ` RFC [patch] sched,cgroup_sched: convince RT_GROUP_SCHED throttle to work Mike Galbraith
2012-04-10 9:08 ` Mike Galbraith
2012-04-14 11:10 ` Peter Zijlstra
2012-04-15 3:37 ` Mike Galbraith
2012-04-15 3:44 ` Mike Galbraith
2012-04-15 4:51 ` Mike Galbraith
2012-04-18 5:20 ` Yong Zhang
2012-04-18 6:27 ` Mike Galbraith [this message]
2012-04-18 7:48 ` Yong Zhang
2012-04-18 8:38 ` Mike Galbraith
2012-04-19 6:34 ` Yong Zhang
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=1334730470.5616.33.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=yong.zhang0@gmail.com \
/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
Powered by JetHome