From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [RFC] [Design] Better XL support of RTDS scheduler for Xen 4.6 Date: Tue, 24 Feb 2015 16:35:48 +0000 Message-ID: <1424795745.4742.128.camel@citrix.com> References: <20150223155724.GB20083@zion.uk.xensource.com> <1424774243.27930.310.camel@citrix.com> <1424775147.4742.56.camel@citrix.com> <1424775992.27930.319.camel@citrix.com> <1424777420.4742.78.camel@citrix.com> <1424787378.27930.352.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8158803124105787213==" Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YQISn-0003p5-Fs for xen-devel@lists.xenproject.org; Tue, 24 Feb 2015 16:36:01 +0000 In-Reply-To: <1424787378.27930.352.camel@citrix.com> Content-Language: en-US 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: Wei Liu , "xen-devel@lists.xenproject.org" , "xisisu@gmail.com" , Ian Jackson , "chaowang@wustl.edu" , George Dunlap , "sokolsky@cis.upenn.edu" , "linhphan@cis.upenn.edu" , "xumengpanda@gmail.com" , "cdgill@cse.wustl.edu" , "lichong659@gmail.com" , "lu.wustl@gmail.com" , "lee@cis.upenn.edu" , "dgolomb@seas.upenn.edu" , "mengxu@cis.upenn.edu" List-Id: xen-devel@lists.xenproject.org --===============8158803124105787213== Content-Language: en-US Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-EZ2JfOUOMlbgth0Bv1xb" --=-EZ2JfOUOMlbgth0Bv1xb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2015-02-24 at 14:16 +0000, Ian Campbell wrote: > On Tue, 2015-02-24 at 11:30 +0000, Dario Faggioli wrote: > > Semantically speaking, they just should be killed. OTOH, what I was > > suggesting was this: if one calls libxl_domain_sched_params_set(), whic= h > > takes a libxl_domain_sched_params, the budget and priod there will be > > interpreted as "for the whole domain", and applied to all the domain's > > vcpus. It's in this sense that I see it an either/or: > > - at domain creation time, if the user does not say anything we'll use > > the domain-wide API for setting a default budget and period for all > > the vcpus. > > - if the user does say something in the config file (once this will be > > possible), or upon request, via the proper xl command, to modify the > > parameters of vcpu X, we'll use the vcpu-wide API. >=20 > The simplest (and IMHO least surprising) thing would be to have the > per-vcpu ones override the per-domain ones.=20 > I agree. > So at build time you would first call the per-domain set function with > whatever parameters were provided, followed by setting any per-vcpu > options which are configured. >=20 Yep. > At run time via xl commands I guess they would be separate commands for > domains vs vcpus,=20 > Yes, either there will be separate commands, or the same command will have a way of specifying whether the parameters are to be considered domain-wide, or just apply to one (or more) vcpus. Still using RTDS as an example, this is what I was suggesting, earlier in this thread (http://www.gossamer-threads.com/lists/xen/devel/368154#368154): # xl sched-rtds -d 4 -p 10000 -b 5000=20 |=20 ---> sets all the vcpus of domain 4 to 5000/10000=20 # xl sched-rtds -d 3 -v 2 -p 5000 -b 2000=20 |=20 ---> set vcpu 2 of domain 4 to 2000/5000=20 # xl sched-rtds -d 2 -v 0 -p 10000 -b 1000 -v 1 -p 5000 -b 2500=20 |=20 ---> set vcpu 0 of domain 2 to 1000/10000 and vcpu 1 of=20 domain 2 to 2500/5000=20 > and if you call the per-domain one I'd probably expect > it to clobber any existing per-vcpu settings (i.e act like the vcpu > option given --all). >=20 Exactly Regards, Dario --=-EZ2JfOUOMlbgth0Bv1xb 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 iEYEABECAAYFAlTsqGEACgkQk4XaBE3IOsSxRgCfVHxnAjpEP2VpqQQOyG8ziGgA SWYAnid/SJ159THMFtWAGCdCpHhwu9Xe =ySQ0 -----END PGP SIGNATURE----- --=-EZ2JfOUOMlbgth0Bv1xb-- --===============8158803124105787213== 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 --===============8158803124105787213==--