From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH 05 of 10 [RFC]] xl: Explicit node affinity specification for guests via config file Date: Fri, 13 Apr 2012 00:25:23 +0200 Message-ID: <1334269523.2417.26.camel@Abyss> References: <7e76233448b02810f0ae.1334150272@Solace> <4F86AD6E.3050705@eu.citrix.com> <4F86B313.5010708@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6842765824549127613==" Return-path: In-Reply-To: <4F86B313.5010708@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: David Vrabel Cc: Andre Przywara , Ian Campbell , Stefano Stabellini , George Dunlap , Juergen Gross , Ian Jackson , "xen-devel@lists.xen.org" , Jan Beulich List-Id: xen-devel@lists.xenproject.org --===============6842765824549127613== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-ixuquBtDMt2N8+2FSNqx" --=-ixuquBtDMt2N8+2FSNqx Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 2012-04-12 at 11:48 +0100, David Vrabel wrote:=20 > > Hmm, I think that using "affine" here is technically correct, and is > > what one would use if writing a research paper; but it's unusual to hea= r > > the word in more common English; it would be more common to hear someon= e > > describe a VM as "having affinity with". How about something like this= : > >=20 > > "The list of NUMA nodes the domain is considered to have affinity with.= =20 > > Memory from the guest will be allocated from these nodes." >=20 > That's clunky sentence, the "considered" doesn't add anything. Or perhap= s: >=20 > "The NUMA nodes preferred by the guest. Memory for the guest will be > allocated on these nodes." >=20 Wow, that is even cooler, thanks! :-) > The need for quotes around the node numbers is odd. Can that > requirement be removed? >=20 I'm not sure I ever checked/tried doing that. It's the plain libxl parser for lists, which I've always seen taking strings in all the examples I found, but I haven't ever looked at the actual code... I'll figure that out and, if possible, get rid of them. I agree they're disturbing. Thanks, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-ixuquBtDMt2N8+2FSNqx 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.12 (GNU/Linux) iEYEABECAAYFAk+HVlMACgkQk4XaBE3IOsRCCwCfcqA+lbuMOUp50er3gSYVSmq8 fcAAnjjgPb682W3ZLccGWfLaTJnV4nT7 =fSDC -----END PGP SIGNATURE----- --=-ixuquBtDMt2N8+2FSNqx-- --===============6842765824549127613== 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 --===============6842765824549127613==--