From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH RESEND 05/12] xen: numa-sched: make space for per-vcpu node-affinity Date: Wed, 6 Nov 2013 00:12:25 +0100 Message-ID: <1383693145.15457.64.camel@Abyss> References: <20131105142844.30446.78671.stgit@Solace> <20131105143500.30446.9976.stgit@Solace> <5279143702000078000FFB15@nat28.tlf.novell.com> <527908B2.5090208@eu.citrix.com> <52790A93.4020903@eu.citrix.com> <52791B8702000078000FFBC4@nat28.tlf.novell.com> <5279114B.9080405@eu.citrix.com> <52792326.4050206@eu.citrix.com> <527927E3.3000004@eu.citrix.com> <5279395302000078000FFD16@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7743879971316511458==" Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VdpnU-0002L3-Gj for xen-devel@lists.xenproject.org; Tue, 05 Nov 2013 23:12:32 +0000 In-Reply-To: <5279395302000078000FFD16@nat28.tlf.novell.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: Jan Beulich Cc: MarcusGranado , Justin Weaver , Ian Campbell , Li Yechen , George Dunlap , Andrew Cooper , JuergenGross , Ian Jackson , Matt Wilson , xen-devel , Daniel De Graaf , KeirFraser , Elena Ufimtseva List-Id: xen-devel@lists.xenproject.org --===============7743879971316511458== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-b253rW4EyAiG0o4ozQak" --=-b253rW4EyAiG0o4ozQak Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-11-05 at 17:30 +0000, Jan Beulich wrote: > >>> On 05.11.13 at 18:16, George Dunlap wro= te: > > This would mean the toolstack either assuming, when someone calls=20 > > vcpu_set_node_affinity, that soft_affinity =3D=3D numa_affinity, or kee= ping=20 > > its own copy of numa_affinity for each vcpu around somewhere. >=20 > Question is how reasonable it is for the tool stack to keep such > information around and up-to-date, in particular considering > node/CPU/memory hotplug. > Right. Well, I may be wrong, and I won't know until I'll actually try coding it (first thing in the morning), but I honestly don't think there will be much to keep around at the toolstack level. > If that's reasonable, then your > proposal below seems to be the right one architecturally, i.e. > keeping policy entirely at the tools level. >=20 Agreed. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-b253rW4EyAiG0o4ozQak 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 v1.4.15 (GNU/Linux) iEYEABECAAYFAlJ5e1kACgkQk4XaBE3IOsQMEQCgmf7weknKFWXoGp0tOfynw1jJ wuIAni4fXJCw3p/ZsO6TPf5LsHHv/IIs =EFZv -----END PGP SIGNATURE----- --=-b253rW4EyAiG0o4ozQak-- --===============7743879971316511458== 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 --===============7743879971316511458==--