xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: "Julien Grall" <julien.grall@arm.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Wei Liu" <wei.liu2@citrix.com>,
	"Jan Beulich" <JBeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] xen/sched: Re-position the domain_update_node_affinity() call during vcpu construction
Date: Tue, 11 Sep 2018 18:14:23 +0200	[thread overview]
Message-ID: <3684cff3526fc2adb160f6b072fac5eebb366944.camel@suse.com> (raw)
In-Reply-To: <1536242495-21173-1-git-send-email-andrew.cooper3@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]

On Thu, 2018-09-06 at 15:01 +0100, Andrew Cooper wrote:
> alloc_vcpu()'s call to domain_update_node_affinity() has existed for
> a decade,
> but its effort is mostly wasted.
> 
> alloc_vcpu() is called in a loop for each vcpu, bringing them into
> existence.
> The values of the affinity masks are still default, which is allcpus
> in
> general, or a processor singleton for pinned domains.
> 
> Furthermore, domain_update_node_affinity() itself loops over all
> vcpus
> accumulating the masks, making it a scalability concern with large
> numbers of
> vcpus.
> 
> Move it to be called once after all vcpus are constructed, which has
> the same
> net effect, but with fewer intermediate memory allocations and less
> cpumask
> arithmetic.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
Reviewed-by: Dario Faggioli <dfaggioli@suse.com>

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2018-09-11 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 14:01 [PATCH] xen/sched: Re-position the domain_update_node_affinity() call during vcpu construction Andrew Cooper
2018-09-07  8:33 ` Jan Beulich
2018-09-07  8:40 ` Wei Liu
2018-09-10 11:27 ` Julien Grall
2018-09-11 16:14 ` 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=3684cff3526fc2adb160f6b072fac5eebb366944.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=julien.grall@arm.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).