From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] SEDF: avoid gathering vCPU-s on pCPU0
Date: Mon, 4 Mar 2013 12:11:34 +0000 [thread overview]
Message-ID: <51348F76.3090204@eu.citrix.com> (raw)
In-Reply-To: <5134959502000078000C2C60@nat28.tlf.novell.com>
On 04/03/13 11:37, Jan Beulich wrote:
> While you might argue that affinity changes ought to be done
> in a "sensible" way, I think you still realize that there is behavior
> here that one wouldn't be able to control without explicitly
> adding an intermediate step when doing this for DomU-s. And
> you should also keep in mind that there are certain things that
> Dom0 needs to change its vCPU affinities for (pv-ops doesn't
> do that, which is while certain things there just can't work);
> this is how I noticed in the first place that the second half of
> the fix is necessary.
Oh right -- so the problem is that when you *expand* the mask, you want
the scheduler to take another look at where might be a good place to run
the vcpu given the changed constraints.
It's probably not a bad idea to just extend that idea to all the
schedulers really. It's not like we expect people to be changing the
affinity masks hundreds of times a second.
-George
next prev parent reply other threads:[~2013-03-04 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 15:35 [PATCH] SEDF: avoid gathering vCPU-s on pCPU0 Jan Beulich
2013-03-01 15:54 ` Keir Fraser
2013-03-02 3:44 ` Ian Campbell
2013-03-04 7:57 ` Jan Beulich
2013-03-05 15:54 ` [PATCH] SEDF: avoid gathering vCPU-s on pCPU0 [and 1 more messages] Ian Jackson
2013-03-05 16:11 ` Jan Beulich
2013-03-04 6:48 ` [PATCH] SEDF: avoid gathering vCPU-s on pCPU0 Juergen Gross
2013-03-04 7:59 ` Jan Beulich
2013-03-04 11:22 ` George Dunlap
2013-03-04 11:37 ` Jan Beulich
2013-03-04 12:11 ` George Dunlap [this message]
2013-03-04 12:23 ` Jan Beulich
2013-03-04 12:15 ` George Dunlap
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=51348F76.3090204@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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 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.