From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: Test result of xen-unstable changeset 25249 Date: Fri, 27 Apr 2012 17:35:24 +0200 Message-ID: <1335540924.2488.73.camel@Abyss> References: <1335435995180-5667212.post@n5.nabble.com> <1335441317.28015.127.camel@zakaz.uk.xensource.com> <20120427082114.GA28258@bloms.de> <4F9A5C79.2090604@eu.citrix.com> <1335517688.28015.180.camel@zakaz.uk.xensource.com> <1335540025.2488.67.camel@Abyss> <1335540505.28015.228.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3719922256132598410==" Return-path: In-Reply-To: <1335540505.28015.228.camel@zakaz.uk.xensource.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: Ian Campbell Cc: George Dunlap , "xen-devel@lists.xensource.com" , Ian Jackson , Dieter Bloms , Fantu List-Id: xen-devel@lists.xenproject.org --===============3719922256132598410== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-dWJhboYq9NnaZ4qAzlqf" --=-dWJhboYq9NnaZ4qAzlqf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2012-04-27 at 16:28 +0100, Ian Campbell wrote:=20 > > It seems to me that, in such case, we will be setting the wrong set of > > parameters anyway, independently on how well we manage in putting a > > default in place for them... Am I missing something? If not, as I > > haven't found any way of finding out what scheduler is actually being > > used for a specific domain, shouldn't we add or mimic that (going > > through cpupool, perhaps, I haven't checked yet)? >=20 > I think you are right. Should we have libxl_gfet_domain_scheduler (or > some such) which implements the appropriate logic? >=20 If we want to keep the patch (and I'm sure we want, as having the possibility to set scheduling parameters in the config file kills a regression against xm, and it's a very nice feature after all :-D) I think we should. I can look into that if you want. I'm also trying to figure out if a default value for the various parameters of the various scheduler can be "elected". It doesn't look like an easy thing to do, e.g., consider sedf wants time values for "period" and "slice", so virtually any unsigned value is meaningful, although, yes, period=3D0 or slice=3D0 barely make sense, and thus maybe we can use these... Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-dWJhboYq9NnaZ4qAzlqf 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+avLwACgkQk4XaBE3IOsQdrQCgo1KUl7ac+uPDjRi/gJ4gX0qo G6IAoIy+WPwakaIu33vxAelFm7D5giGp =8YBm -----END PGP SIGNATURE----- --=-dWJhboYq9NnaZ4qAzlqf-- --===============3719922256132598410== 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 --===============3719922256132598410==--