From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [Hackathon minutes] PV frontends/backends and NUMA machines Date: Tue, 21 May 2013 13:12:33 +0200 Message-ID: <1369134753.12423.65.camel@Solace> References: <20130521083251.GD9626@ocelot.phlegethon.org> <20130521092003.GE9626@ocelot.phlegethon.org> <519B4241.2040006@eu.citrix.com> <20130521102409.GH9626@ocelot.phlegethon.org> <519B4C64.40806@eu.citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5404985294998595700==" Return-path: In-Reply-To: <519B4C64.40806@eu.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: George Dunlap Cc: "xen-devel@lists.xensource.com" , Tim Deegan , Matt Wilson , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org --===============5404985294998595700== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tu1wV82q1n6wOndF8fb3" --=-tu1wV82q1n6wOndF8fb3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-05-21 at 11:28 +0100, George Dunlap wrote: > On 05/21/2013 11:24 AM, Tim Deegan wrote: > > At 10:45 +0100 on 21 May (1369133137), George Dunlap wrote: > >> What we would want for a comparable domU -- a domU that was NUMA-aware > >> -- was to have the pfn layout in batches across the nodes to which it > >> will be pinned. E.g., if a domU has its NUMA affinity set to nodes 2-= 3, > >> then you'd want the first half of the pfns to come from node 2, the > >> second half from node 3. > >> > >> In both cases, the domain builder will need to call the allocator with > >> specific numa nodes for specific regions of the PFN space. > > > > Ah, so that logic lives in the tools for domU? I was misremembering. > > Anyway, I think I'm convinced that this is a reasonable thing to do > > the dom0 building code. :) >=20 > I don't think it lives anywhere at the moment --=20 > Yep, the issue is there is no such logic at all yet! :-P > I think at the moment=20 > the domain builder for both dom0 and domU just call the allocator=20 > without any directions, and the allocator reads the NUMA affinity mask= =20 > for the domain. > And stripes the allocation through such mask, yes, without caring at all where specific regions end up... Actually, without knowing anything about 'specific regions'. > But yes, when we do get guest NUMA support, I think the=20 > domain builder will be the right place to set up the guest NUMA layout,= =20 > both for domUs and dom0. >=20 +1 > Matt Wilson I think has some patches to do the domU layout for HVM=20 > guests -- if he could post those at some point in the next month, it=20 > might give a head start to the person implementing this (probably me at= =20 > this point). >=20 Yes, that would surely help. In the meantime, I replied to your first e-mail in this thread with the links to all the old patches I've been able to find on this subject... Hope that helps too. :-) Regards, Dario --=-tu1wV82q1n6wOndF8fb3 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.13 (GNU/Linux) iEYEABECAAYFAlGbVqEACgkQk4XaBE3IOsSgZACgnMn1X7Alzq6CZxwMI77SjSSi B0QAnRX1iXo7QjHSvpPFEfDfkxzjhfdb =iVXF -----END PGP SIGNATURE----- --=-tu1wV82q1n6wOndF8fb3-- --===============5404985294998595700== 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 --===============5404985294998595700==--