From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: Granularity of Credit and RTDS Scheduler
Date: Wed, 11 Jan 2017 18:29:42 +0100
Message-ID: <1484155782.32021.139.camel@citrix.com>
References: <20170106123448.Horde.7ljmZcV3GlmCwOs-VqzuWg2@webmail.rice.edu>
 <CAENZ-+=4-Qkq6t853KA53BwZeT+NJYCCbKd8Rv-GGfhp6vySfQ@mail.gmail.com>
 <20170110153207.Horde.KQybalzWl-SjnpU0RzIXjw1@webmail.rice.edu>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4757459172648936703=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20170110153207.Horde.KQybalzWl-SjnpU0RzIXjw1@webmail.rice.edu>
List-Unsubscribe: <https://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: <https://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
 <mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Errors-To: xen-devel-bounces@lists.xen.org
Sender: "Xen-devel" <xen-devel-bounces@lists.xen.org>
To: wy11 <wy11@rice.edu>, Meng Xu <xumengpanda@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

--===============4757459172648936703==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="=-bTjoxtljaYkBzTyVMo89"

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

On Tue, 2017-01-10 at 15:32 -0600, wy11 wrote:
> If the time granularity of RTDS is nanosecond, then it is no longer
> a=C2=A0=C2=A0
> problem. Can you please help me to know where I can find it in the=C2=A0=
=C2=A0
> source code?
>=20
If that's what you're interested in, time granularity is nanoseconds
for each and every scheduler.

Look at xen/common/schedule.c, xen/common/sched_credit.c,
xen/common/sched_credit2.c and xen/common/sched_rt.c, and see how they
all use the NOW() macro for reading time.

Then go checking how NOW() is defined.

Regards,
Dario
--=20
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
--=-bTjoxtljaYkBzTyVMo89
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

iQIcBAABCAAGBQJYdmuHAAoJEBZCeImluHPucL4P/1BO/7TxFDyh1nx3N1w5X2Wp
kFJms+AWAZ+3NmjicyCxtE9wynUmdbpse1o40Asd0tzzOkEtHl54+AEpmnkwUwMv
2gCjKn5GrxBPbjAitKeFuPQ9jNLd/qayvJxypwV8FWsUdrQpraZVvfV2+AOGgcBx
x+4gaS6gENfgveYYaA8Y/BtZsafa9kVLzBT5ai9p2EPVfr/MGWlplyjSrDIHwwiR
2zc3Ega6UcL95rDeMfbxVX33Ud01At3ZjsTWhLKmSUi3/thlB8phjoW1JHS2sNX4
BdFEfXB8u5b+wPfhHT5BwaUTpE+dl5IpiHYq9qyK4O5caekfIKRKlQtYzIcp4Lgw
YkgizPVacU3bVGXJLRLIt/b/Jw50fFg2EzH+k4saMcwKJ0OQ0v+juSet1VxUBIVl
1zvjDOfp6lY+f/5U6G3kN9466gp3+BhCgPZoE3v/0npIqHklu7SXhfS/U+8L1OAb
P/A52LFHRwWnXEARVGa9O8rN/d8XdaZjVBy0ZYl0CDigfuuPXAtL2T6rGyA2i95C
r44/b12UJ/K3BjoYxyvt9X4xbNlLlqZhYJIXH4SIVrAWxngTFvG/weNXswbSkNPQ
iPGdKcnvfP+L6nAI+hCMI7IE0GHONHqpJiGPwzLikcOARKL2zcnV8ERFkaanzZhW
sGugCVq0LIbYHewX7N4n
=niJu
-----END PGP SIGNATURE-----

--=-bTjoxtljaYkBzTyVMo89--


--===============4757459172648936703==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs
IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v
cmcveGVuLWRldmVsCg==

--===============4757459172648936703==--