From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH 1/5] x86: allow specifying the NUMA nodes Dom0 should run on Date: Fri, 06 Mar 2015 12:33:22 +0100 Message-ID: <1425641602.12503.47.camel@gmail.com> References: <54EF315902000078000640FF@mail.emea.novell.com> <54EF3348020000780006413C@mail.emea.novell.com> <1424970840.4742.228.camel@citrix.com> <54F03CE0020000780006472F@mail.emea.novell.com> <1425031468.10194.43.camel@citrix.com> <54F05A0C0200007800064878@mail.emea.novell.com> <1425048895.10194.108.camel@citrix.com> <54F5A047020000780006592F@mail.emea.novell.com> <54F97D420200007800066DC1@mail.emea.novell.com> <1425638814.12503.12.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5882541342674392795==" Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YTqVX-0004Ww-JG for xen-devel@lists.xenproject.org; Fri, 06 Mar 2015 11:33:31 +0000 Received: by wevk48 with SMTP id k48so12224510wev.5 for ; Fri, 06 Mar 2015 03:33:27 -0800 (PST) In-Reply-To: <1425638814.12503.12.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "JBeulich@suse.com" Cc: "Keir (Xen.org)" , Ian Campbell , Andrew Cooper , "Tim (Xen.org)" , "xen-devel@lists.xenproject.org" , Ian Jackson List-Id: xen-devel@lists.xenproject.org --===============5882541342674392795== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-QvtCg1yu/LzDDOY/C6aO" --=-QvtCg1yu/LzDDOY/C6aO Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2015-03-06 at 10:46 +0000, Dario Faggioli wrote: > On Fri, 2015-03-06 at 09:11 +0000, Jan Beulich wrote: > > >>> On 03.03.15 at 11:51, wrote: > > Having implemented this "relaxed" addition (patch to be posted after > > a few more tests), I find that with Dom0 being restricted to half of > > the nodes of the test system, soft affinity set to that set, and hard > > affinity left set to "all", many Dom0 vCPU-s nevertheless run on the > > CPUs not in its soft affinity (and there's no other load on the system)= . > Oh, BTW, in my previous email I was asking about system load because, while replying, I missed this: "there's no other load on the system"... sorry! :-/ > > Is there a bug in that (credit) scheduler logic somewhere? > >=20 > There may be, of course, but nothing showed up during testing and > benchmarking the feature. It's true that I probably concentrate mostly > on DomU (especially while benchmarking), but it worked for me, and > numbers from benchmarks confirmed that. > I'm testing soft affinity for Dom0 _without_ your patches, i.e., I'm just setting soft affinity for Dom0's vCPUs after boot (hard affinity set to "all") and looking at where they executes, both with and without other load, and results look consistent to me. I see Dom0 vCPUs executing almost only on pCPUs from their soft affinity set, at least all the times that this is possible. If I generate other vCPU load aimed at kicking them away from there, they do go away, but they come back to such set as soon as the load disappears. So, soft affinity per-se seems to be working for me. I'll now apply your patch and see whether that changes thing (seems unlikely, though). If you want me to try replicate some specific testing scenario, feel free to provide more details about it and I'll give it a go. :-) Regards, Dario --=-QvtCg1yu/LzDDOY/C6aO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlT5kIIACgkQk4XaBE3IOsQTDwCfaKveHCoFXUsF/6o5nW3T2tns +hgAoJoovPjcMRoQRV6oz0PqMXCxzF4G =1t60 -----END PGP SIGNATURE----- --=-QvtCg1yu/LzDDOY/C6aO-- --===============5882541342674392795== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============5882541342674392795==--