From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH 00 of 10 v3] Automatic NUMA placement for xl Date: Mon, 09 Jul 2012 16:32:43 +0200 Message-ID: <1341844363.3657.9.camel@Abyss> References: <1341772341.797.1.camel@hastur.hellion.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4281168883698067216==" Return-path: In-Reply-To: <1341772341.797.1.camel@hastur.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Andre Przywara , Stefano Stabellini , George Dunlap , Juergen Gross , Ian Jackson , "xen-devel@lists.xen.org" , Roger Pau Monne List-Id: xen-devel@lists.xenproject.org --===============4281168883698067216== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-qkH7bz/BfhPF1dYQpYF9" --=-qkH7bz/BfhPF1dYQpYF9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, 2012-07-08 at 12:32 -0600, Ian Campbell wrote:=20 > On Wed, 2012-07-04 at 12:17 -0400, Dario Faggioli wrote: > > Hello, > >=20 > > Third version of the NUMA placement series Xen 4.2. >=20 > Starting an HVM guest (although I don't suppose it is HVM specific) on a > none NUMA system I get this: >=20 > libxl: debug: libxl_numa.c:270:libxl__get_numa_candidates: only 1= node. no placement required > libxl: detail: libxl_dom.c:175:numa_place_domain: 0 NUMA placemen= t candidates found > libxl: notice: libxl_dom.c:180:numa_place_domain: NUMA placement = failed, performance might be affected > =20 Mmm... I see. No, it's not HVM specific and you're right, it does not make much sense. > this being a non-NUMA system I suppose it is not the end of the world. > It'd be nice to avoid the warning though -- perhaps > libxl__get_numa_candidates should either not special case single node > systems or it should manually return the trivial candidate set? >=20 Yep, I can definitely do that, along with the other fix you suggested and the wording of the doc patch and resend the last three. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-qkH7bz/BfhPF1dYQpYF9 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/664wACgkQk4XaBE3IOsTE1gCcD0Nb0VUTG7FHmltm4Zk/ZUez WyEAnRLb+ynnihWDD0Ep3mS4oYETrK90 =CIFS -----END PGP SIGNATURE----- --=-qkH7bz/BfhPF1dYQpYF9-- --===============4281168883698067216== 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 --===============4281168883698067216==--