From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH RFC v1 2/3] libxl: enable per-VCPU work conserving flag for RTDS Date: Fri, 4 Aug 2017 22:47:42 +0200 Message-ID: <1501879662.11046.8.camel@citrix.com> References: <1501612434-5803-1-git-send-email-mengxu@cis.upenn.edu> <1501612434-5803-3-git-send-email-mengxu@cis.upenn.edu> <1501775614.28477.10.camel@citrix.com> <1501834398.28477.14.camel@citrix.com> <20170804121019.l3jsw3zb7briwf2y@citrix.com> <1501851231.11046.4.camel@citrix.com> <20170804143425.pejmv426acduut55@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4220801733152507634==" Return-path: Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ddjW4-0008B4-2B for xen-devel@lists.xenproject.org; Fri, 04 Aug 2017 20:48:16 +0000 In-Reply-To: <20170804143425.pejmv426acduut55@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Wei Liu Cc: George Dunlap , "xen-devel@lists.xenproject.org" , Meng Xu , Ian Jackson List-Id: xen-devel@lists.xenproject.org --===============4220801733152507634== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="=-ZaGrtjxahD6B5RXDYOwP" --=-ZaGrtjxahD6B5RXDYOwP Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2017-08-04 at 15:34 +0100, Wei Liu wrote: > On Fri, Aug 04, 2017 at 02:53:51PM +0200, Dario Faggioli wrote: > >=20 > > Well, I guess yes. But how does this matter? Each scheduler can, if > > it > > wants, use all these parameters in the way it actuallly prefers. > > So, > > the fact that RTDS will be using 'extratime' for letting vCPUs > > execute > > past their own real-time reservation, does not prevent the > > reintroduced > > SEDF --nor any other already existing or new scheduler-- to also > > use > > it, for similar (or maybe even not so similar) purposes. > >=20 > > Or am I missing something? >=20 > If extratime means different things to different schedulers, it's > going > to be confusing. As a layperson I can't tell what extratime is or how > it > is supposed to be used. I would like to have the field to have only > one > meaning. > Well, I do see what you mean, but then I don't understand why we have the data structure organized like this, i.e., with all the parameters for all the schedulers in the same struct. IAC: - extratime was only used by SEDF - SEDF is not coming back, at least not in the form it had when it was removed, because it was bitrotten and buggy, and RTDS has actually replaced it - if a correct version of SEDF would ever come back, and live alongside with RTDS, both the schedulers would use extratime to mean the same (although, of course, actual use and implementation may vary) This should be enough to address your concerns. Let me know if it's not. :-) Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-ZaGrtjxahD6B5RXDYOwP 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 v2 iQIcBAABCAAGBQJZhN1uAAoJEBZCeImluHPul8MP/0dDYoYt+ca3PagLtbQSCDDM PqmIyRs8M4UrHHzzkG+9Yx3UxyFsIrUN5ut4dC3hxepVRdDrl6AgNzxqUeHBnY53 i0WBNS1DUe5v1Rv4O/HnE+ux0oOTqNp4nDAkCnKdJ3CnHLXUCPXF8KxCN32Q44zK AO5SS8GytG3gjMoOJ8DNHDvkrFqWjiNqXb4BIMvmRABFIfUPJ2fVJBPu69YOpymL qef7OjAMljslXdcZ4Ju2krjK7K0SUorMPYiuKtPfqE8RQUlKP9kLRHrOhkKOUOst gml991EqwDz/xLuYBdJfoAjnVOtNWDg1Hup8a2hKdA+lJ5gHw/OO0UvYvwqNbP31 w00pZ/4w4jlaTFGgEp3fQKruQtA75sBQAUsKffeA2FSxOcsqYnyM63BNvpgJerhD fpeQJA1onZwslCsXuug/fYmKJr2+smlMEOSYhUjsQeqcUavKHCOGMDmLZWQydRb9 rLTXWhsVJJjQXeyffJP7J5aF2ZHtG+gdSncGyJfEXHRXDTZ60aKWvJiEOxt0v7rF AcwjcKHdrtMN16PFRSV3mUp13G+Hj33ddxsFi8Cr4XnOoeKYuvZHiLKY5Ix46OqS l70r85lZdFFhfQg269zgsc0WUr6HdTglS55LCSEp9Zb2FWt46li1cuUckudkU/Hu ZSrxqjHobQs/2thvADzm =0DzX -----END PGP SIGNATURE----- --=-ZaGrtjxahD6B5RXDYOwP-- --===============4220801733152507634== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============4220801733152507634==--