From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@kernel.org>, Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: linux-next: new scheduler messages span: 0-15 (max cpu_capacity = 589) when starting KVM guests
Date: Mon, 19 Sep 2016 15:19:11 +0200 [thread overview]
Message-ID: <e399c212-50f2-56ec-d3e6-27d3742b4917@de.ibm.com> (raw)
Dietmar, Ingo, Tejun,
since commit cd92bfd3b8cb0ec2ee825e55a3aee704cd55aea9
sched/core: Store maximum per-CPU capacity in root domain
I get tons of messages from the scheduler like
[..]
span: 0-15 (max cpu_capacity = 589)
span: 0-15 (max cpu_capacity = 589)
span: 0-15 (max cpu_capacity = 589)
span: 0-15 (max cpu_capacity = 589)
[..]
whenever I start kvm guests with libvirt.
The reason seems to be that libvirt via systemd/machined tries to move all
guest vcpus into its cpuset and for whatever reasons, the way it is done
will always call rebuild_sched_domains from the cgroup code.
While the message alone is somewhat of a nuisance, I think rebuilding
the scheduling domains for moving kvm vcpus is really expensive.
Tejun, do you have an idea whats going on here? Is libvirt using
the cgroup interface wrong (e.g. also d a memory migrate or whatever)
Christian
next reply other threads:[~2016-09-19 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 13:19 Christian Borntraeger [this message]
2016-09-19 13:40 ` Peter Zijlstra
2016-09-19 13:58 ` Dietmar Eggemann
2016-09-19 14:01 ` Christian Borntraeger
2016-09-20 7:43 ` Christian Borntraeger
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=e399c212-50f2-56ec-d3e6-27d3742b4917@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®