From: George Dunlap <george.dunlap@eu.citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
George Dunlap <George.Dunlap@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"JBeulich@suse.com" <JBeulich@suse.com>
Subject: Re: [PATCH v2] credit: generalize __vcpu_has_soft_affinity()
Date: Fri, 6 Mar 2015 11:38:16 +0000 [thread overview]
Message-ID: <54F991A8.7090206@eu.citrix.com> (raw)
In-Reply-To: <1425640326.12503.32.camel@citrix.com>
On 03/06/2015 11:12 AM, Dario Faggioli wrote:
> On Fri, 2015-03-06 at 09:53 +0000, George Dunlap wrote:
>> On 03/06/2015 07:36 AM, Jan Beulich wrote:
>
>> It looks like the comment above this line could use changing too;
>>
> It probably does.
>
>> ---
>> Hard affinity balancing is always necessary and must never be skipped.
>> But soft affinity need only be considered when it has a functionally
>> different effect than other constraints (such as hard affinity, cpus
>> online, or cpupools).
>>
>> Soft affinity only needs to be considered if:
>> * The cpus in the cpupool are not a subset of soft affinity
>> * The hard affinity is not a subset of soft affinity
>> * There is an overlap between the soft affinity and the mask which is
>> currently being considered.
>> ---
> The original comment was more aimed at trying to make as evident as
> possible to the reader why the occurrence of a particular combination of
> hard and soft affinity makes using the latter pointless (perhaps it was
> not that effective at that, but that's another story! :-D).
>
> So, if changing it, I'd go for something more 'high level'; something
> that helps the reader grasp more quickly what is the actual meaning of
> those _subsect() and _intersect() operations. Perhaps:
>
> ---
> Hard affinity balancing is always necessary and must never be skipped.
> Soft affinity balancing is only useful if it, potentially, makes a
> difference.
>
> In more details, there is no point checking soft affinity if:
> * there is no online pCPU in the domain's cpupool that is not in the
> soft affinity mask
> * there is no pCPU in the hard affinity mask that is not in the soft
> affinity mask
> * there is no overlapping between the soft affinity mask and the mask
> being considered (which, in most cases, is the hard affinity mask)
> ---
I think what you've said here is almost exactly the same thing as what I
said, except using different words. (i.e., "X not a subset of Y" means
"there are X which are not in Y")
I don't mind necessarily, but I'm not sure you've actually accomplished
your purpose. :-)
-George
next prev parent reply other threads:[~2015-03-06 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 7:36 [PATCH v2] credit: generalize __vcpu_has_soft_affinity() Jan Beulich
2015-03-06 8:39 ` Dario Faggioli
2015-03-06 9:53 ` George Dunlap
2015-03-06 10:16 ` Jan Beulich
2015-03-06 11:32 ` George Dunlap
2015-03-06 11:44 ` Jan Beulich
2015-03-06 12:00 ` George Dunlap
2015-03-06 13:10 ` Jan Beulich
2015-03-06 13:23 ` Dario Faggioli
2015-03-06 13:32 ` Jan Beulich
2015-03-06 13:44 ` Dario Faggioli
2015-03-06 11:12 ` Dario Faggioli
2015-03-06 11:38 ` George Dunlap [this message]
2015-03-06 13:31 ` Dario Faggioli
2015-03-06 14:57 ` George Dunlap
2015-03-06 15:10 ` Dario Faggioli
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=54F991A8.7090206@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.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.