From: Dario Faggioli <dario.faggioli@citrix.com>
To: "JBeulich@suse.com" <JBeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
George Dunlap <George.Dunlap@citrix.com>
Subject: Re: [PATCH v3] credit: generalize __vcpu_has_soft_affinity()
Date: Fri, 6 Mar 2015 14:54:46 +0000 [thread overview]
Message-ID: <1425653684.16932.2.camel@citrix.com> (raw)
In-Reply-To: <54F9B9B602000078000670AB@mail.emea.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 946 bytes --]
On Fri, 2015-03-06 at 13:29 +0000, Jan Beulich wrote:
> As pointed out in the discussion of the patch at
> http://lists.xenproject.org/archives/html/xen-devel/2015-02/msg03256.html
> generalizing the conditions here means code elsewhere doesn't need to
> take into consideration internals of how load balancing in the credit
> scheduler works.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>
> ---
> v3: Swap soft and hard affinities in the 2nd of the 3 checks. Alter
> comment as requested by George (which made us notice the need for
> the code change, therefore retaining his review tag).
> v2: Use VCPU2ONLINE(vc) (or really an open coded variant thereof)
> instead of cpu_online_map (suggested by Dario).
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
This time, hopefully, without having overlooked anything! :-)
Regards,
Dario
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-03-06 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 13:29 [PATCH v3] credit: generalize __vcpu_has_soft_affinity() Jan Beulich
2015-03-06 14:54 ` Dario Faggioli [this message]
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=1425653684.16932.2.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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.