From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH] credit: Change default timeslice to 5ms Date: Thu, 6 Mar 2014 13:27:56 +0100 Message-ID: <1394108876.16409.54.camel@Solace> References: <1394036976-484-1-git-send-email-george.dunlap@eu.citrix.com> <53175C5C.4060505@citrix.com> <5318644A.2060904@eu.citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4263438154093037986==" Return-path: In-Reply-To: <5318644A.2060904@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: Marcus Granado , Keir Fraser , Tim Deegan , xen-devel@lists.xen.org, David Vrabel , Jan Beulich List-Id: xen-devel@lists.xenproject.org --===============4263438154093037986== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-m2D3wAwlcIypl+3tztIs" --=-m2D3wAwlcIypl+3tztIs Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On gio, 2014-03-06 at 12:04 +0000, George Dunlap wrote: > On 03/05/2014 05:18 PM, David Vrabel wrote: > > On 05/03/14 16:29, George Dunlap wrote: > >> --- a/xen/common/sched_credit.c > >> +++ b/xen/common/sched_credit.c > >> @@ -29,9 +29,9 @@ > >> * Basic constants > >> */ > >> #define CSCHED_DEFAULT_WEIGHT 256 > >> -#define CSCHED_TICKS_PER_TSLICE 3 > >> -/* Default timeslice: 30ms */ > >> -#define CSCHED_DEFAULT_TSLICE_MS 30 > >> +#define CSCHED_TICKS_PER_TSLICE 1 > > The TICKS_PER_TSLICE change doubles the tick rate. Is this intentional= ? > > It's not mentioned in the commit message. >=20 > Hmm -- actually, I just realized that Marcus' test was done with 3 ticks= =20 > per timeslice, so "5ms / 1 tick" has *not* been validated. And this is= =20 > actually important, because the main purpose of the ticks is to give the= =20 > scheduler an opportunity to switch VMs out of "BOOST" priority and into= =20 > "UNDER" priority. Reducing the ticks per timeslice changes that=20 > dynamic, and would need to be tested separately. >=20 Which is even higher tick frequency, isn't it? Anyway, you're right, we should go for the tested solution. > Also, I just discovered a rather pathological case in general that seems= =20 > to be in the scheduler, so for the time being let me retract this while= =20 > I figure that out. >=20 Care to share some more details about this? Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-m2D3wAwlcIypl+3tztIs 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.0.22 (GNU/Linux) iEYEABECAAYFAlMYacwACgkQk4XaBE3IOsSUsQCfVTe33RjBmqlyCCr42pp4HBhz uJEAn23VDK5C+nPyIiDeTfQ+dzAg5QHS =MkO8 -----END PGP SIGNATURE----- --=-m2D3wAwlcIypl+3tztIs-- --===============4263438154093037986== 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 --===============4263438154093037986==--