From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/3] libxl: automatically set soft affinity after vnuma info
Date: Tue, 24 Mar 2015 15:06:24 +0000 [thread overview]
Message-ID: <1427209581.2560.209.camel@citrix.com> (raw)
In-Reply-To: <20150324143259.GB30219@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2161 bytes --]
On Tue, 2015-03-24 at 14:32 +0000, Wei Liu wrote:
> On Tue, Mar 24, 2015 at 02:42:15PM +0100, Dario Faggioli wrote:
> > More specifically, vcpus are assigned to a vnode, which in
> > turn is associated with a pnode. If a vcpu does not have any
> > soft affinity, automatically build up one, matching the pcpus
> > of the said pnode.
> >
>
> What about hard affinity? Do we need to generate hard affinity map as
> well? What's your thought on this?
>
I think we should not do that. Hard affinity has a bigger impact on the
system performance and overall configuration than soft, which is really
just a preference, so I would let the user deal with that explicitly.
For example, setting the hard affinity to the same set of pcpus for
multiple domains could, depending on the system load, prevent some of
(the vcpus of) these domain to be able to execute for quite some time,
while there are idle pcpus in the system. This may well be something the
user wants, but I'd let him say so, if that is the case, rather than
automatically setup things like that for everyone! By only affecting
soft affinity, that doesn't happen, and we stay work conserving by
default, which is important.
Also, only touching soft affinity is exactly what automatic NUMA
placement already does, which in turn is consistent with using the
result of placement to influence the domain's node affinity (i.e., what
Xen 4.3 and 4.4 do, since soft affinity was not there), and it is the
best solution, IMO.
Perhaps we can have another config option, telling whether one wants
vnuma (and/or automatic placement) to affect soft or hard affinity (or
both). I'm not sure how much this would be useful, while it would
certainly make things more complex from both the implementation and the
interface point of view (the latter being the more concerning aspect).
In any case, we can add this at any point in future, if we feel it could
be useful, and I still think the default setting --if such option is not
specified-- should remain "affect soft affinity only".
> The code itself looks good to me.
>
Thanks for looking at it. :-)
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
next prev parent reply other threads:[~2015-03-24 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 13:41 [PATCH 0/3] Automatically derive soft affinity from vnuma information Dario Faggioli
2015-03-24 13:41 ` [PATCH 1/3] libxl: check whether vcpu affinity and vnuma info match Dario Faggioli
2015-03-24 14:41 ` Wei Liu
2015-03-24 15:47 ` Dario Faggioli
2015-03-24 15:56 ` Wei Liu
2015-03-24 13:42 ` [PATCH 2/3] libxl: automatically set soft affinity after vnuma info Dario Faggioli
2015-03-24 14:32 ` Wei Liu
2015-03-24 15:06 ` Dario Faggioli [this message]
2015-03-24 15:23 ` Wei Liu
2015-03-24 13:42 ` [PATCH 3/3] libxl: cleanup some misuse of 'cpumap' as parameter Dario Faggioli
2015-03-24 14:33 ` Wei Liu
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=1427209581.2560.209.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=wei.liu2@citrix.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.