From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <raistlin@linux.it>
Subject: Re: NUMA TODO-list for xen-devel
Date: Fri, 03 Aug 2012 15:14:04 +0200
Message-ID: <1343999644.11787.9.camel@Abyss>
References: <1343837796.4958.32.camel@Solace> <501BA1C0.7040100@amd.com>
	<501BC6B8020000780009277B@nat28.tlf.novell.com>
	<501BB54E.1050302@amd.com>
	<501BD46402000078000927F9@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7029823554544432922=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <501BD46402000078000927F9@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Andre Przywara <andre.przywara@amd.com>, Anil Madhavapeddy <anil@recoil.org>, George Dunlap <George.Dunlap@eu.citrix.com>, Andrew Cooper <Andrew.Cooper3@citrix.com>, xen-devel <xen-devel@lists.xen.org>, Yang Z Zhang <yang.z.zhang@intel.com>
List-Id: xen-devel@lists.xenproject.org


--===============7029823554544432922==
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-OcrXWu5uAJdLW1T+Lk6D"


--=-OcrXWu5uAJdLW1T+Lk6D
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2012-08-03 at 12:38 +0100, Jan Beulich wrote:=20
> >> How about "dom0_mem=3Dnode<n> dom0_vcpus=3Dnode<n>" as
> >> an extension to the current options?
> >=20
> > Yes, that sounds like a good idea. And relatively easy to implement.
> > Maybe a list or a number of nodes (to make it more complicated ;-)
>=20
> Oh yes, of course I implied this flexibility. Just wanted to give
> an easy to read example.
>=20
Yep, I agree it sounds nice and should be not to hard. I'll update the
Wiki page.

I only have one question, should we try to take IONUMA into account here
as well? I mean, if it turns out that I/O hubs are connected to some
specific node(s), shouldn't we consider pinning/"affining" Dom0 to those
node(s), as it most likely will be responsible for some/most DomUs' I/O?

Thanks and Regards,
Dario

--=20
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)



--=-OcrXWu5uAJdLW1T+Lk6D
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)

iEYEABECAAYFAlAbzpwACgkQk4XaBE3IOsQkVACeP6/51ZXEqLiXLGnBdHTTZW1F
/aAAniUjq/9sAKL72MztTk9IgSmNDtGS
=sPRo
-----END PGP SIGNATURE-----

--=-OcrXWu5uAJdLW1T+Lk6D--



--===============7029823554544432922==
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

--===============7029823554544432922==--