xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Robbie VanVossen <robert.vanvossen@dornerworks.com>
Cc: Pavlo Suikov <pavlo.suikov@globallogic.com>,
	Nate Studer <nate.studer@dornerworks.com>,
	xen-devel@lists.xen.org
Subject: Re: Delays on usleep calls
Date: Fri, 7 Feb 2014 10:22:16 +0100	[thread overview]
Message-ID: <1391764936.9917.58.camel@Solace> (raw)
In-Reply-To: <52F2AD63.7030109@dornerworks.com>


[-- Attachment #1.1: Type: text/plain, Size: 2653 bytes --]

On mer, 2014-02-05 at 16:30 -0500, Robbie VanVossen wrote:
> On 1/20/2014 10:05 AM, Dario Faggioli wrote:
> > What about giving a try to it yourself? I think standardizing on one (a
> > set of) specific tool could be a good thing.
> 
> Dario,
> 
Hey! :-)

> We thought we would try to get some similar readings for the Arinc653 scheduler.
> We followed your suggestions from this thread and have gotten some readings for
> the following configurations:
> 
That's cool, thanks for doing this and sharing the results.

> We used the following command to get results for a 30 millisecond (30,000us)
> interval with 500 loops:
> 
> cyclictest -t1 -i 30000 -l 500 -q
> 
> Results:
> 
> +--------+--------+-----------+-------+-------+-------+
> | Config | Domain | Scheduler |      Latency (us)     |
> |        |        |           |   Min |   Max |   Avg |
> +--------+--------+-----------+-------+-------+-------+
> |      1 |      0 |  Arinc653 |    20 |   163 |    68 |
> |      2 |      0 |  Arinc653 |    21 |   173 |    68 |
> |      3 |      1 |  Arinc653 |    20 |   155 |    75 |
> +--------+--------+-----------+-------+-------+-------+
> 
> It looks like we get negligible latencies for each of these simplistic
> configurations.
> 
It looks indeed. You're right, the configuration are simplistic. Yet, as
stated before, latency and jitter in scheduling/event response has two
major contributors: one is the scheduling algorithm itself, the other is
the interrupt/event delivery latency of the platform (HW + HYP + OS).
This means that, of course, you need to pick the right scheduler and
configure it properly, but there may be other sources of latency and
delay, and that is what sets the lowest possible limit, unless you go
chasing and fix these 'platform issues'.

From your experiments (an from some other numbers I also have) it looks 
like this lower bound is not terrible in Xen, which is something good to
know... So thanks again for taking the time of running the benchmarks
and sharing the results! :-D

That being said, especially if we compare to baremetal, I think there is
some room for improvements (I mean, there always will be an overhead,
but still...). Do you, by any chance, have the figures for cyclictest on
Linux baremetal too (on the same hardware and kernel, if possible)?

Thanks a lot again!
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: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-02-07  9:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 14:10 Delays on usleep calls Pavlo Suikov
2014-01-20 15:05 ` Dario Faggioli
2014-01-20 16:05   ` Pavlo Suikov
2014-01-20 17:31     ` Pavlo Suikov
2014-01-21 10:56       ` Dario Faggioli
2014-01-21 11:46     ` Dario Faggioli
2014-01-21 15:53       ` Pavlo Suikov
2014-01-21 17:56         ` Dario Faggioli
2014-01-23 19:09           ` Pavlo Suikov
2014-01-24 17:08             ` Dario Faggioli
2014-02-05 21:30   ` Robbie VanVossen
2014-02-07  9:22     ` Dario Faggioli [this message]
2014-02-13 21:09       ` Robbie VanVossen

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=1391764936.9917.58.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=nate.studer@dornerworks.com \
    --cc=pavlo.suikov@globallogic.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).