From: Dario Faggioli <dario.faggioli@citrix.com>
To: wy11 <wy11@rice.edu>, Meng Xu <xumengpanda@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: Granularity of Credit and RTDS Scheduler
Date: Wed, 11 Jan 2017 18:29:42 +0100 [thread overview]
Message-ID: <1484155782.32021.139.camel@citrix.com> (raw)
In-Reply-To: <20170110153207.Horde.KQybalzWl-SjnpU0RzIXjw1@webmail.rice.edu>
[-- Attachment #1.1: Type: text/plain, Size: 818 bytes --]
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
> problem. Can you please help me to know where I can find it in the
> source code?
>
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
--
<<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)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-11 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 18:34 Granularity of Credit and RTDS Scheduler wy11
2017-01-08 7:30 ` Meng Xu
2017-01-10 21:32 ` wy11
2017-01-10 21:49 ` Meng Xu
2017-01-11 17:29 ` Dario Faggioli [this message]
2017-01-11 17:57 ` wy11
-- strict thread matches above, loose matches on Subject: below --
2017-01-08 22:06 Dario Faggioli
2017-01-13 8:37 ` Dario Faggioli
2017-01-14 17:51 ` wy11
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1484155782.32021.139.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=wy11@rice.edu \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.