From: Jan Kiszka <jan.kiszka@domain.hid>
To: Li Yi <yi.li@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] question about the latency test running on Blackfin
Date: Wed, 12 Apr 2006 09:46:52 +0200 [thread overview]
Message-ID: <443CB06C.2080202@domain.hid> (raw)
In-Reply-To: <1144809772.7286.47.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
Li Yi wrote:
> Hi Philippe,
>
> According to your answers, I updated the document on Xenomai on
> Blackfin: (http://docs.blackfin.uclinux.org/doku.php?id=adeos) with the
> test result of different modes, setting XENO_OPT_TIMING_SCHEDLAT = 1.
> But I still have some question about the test result, hoping for your
> help:
>
> When running this test in mode 0, the worst case latency is 65 us, (HSD|
> max| 65 - 66 | 1). This result is get when there is no workload. Can I
> say this system is "Hard Real-time" because most of the latency samples
> are in a limited range?
Soft RT: the more samples remain under the required limit the higher is
the quality of the system
Hard RT: ALL samples must be below the limit
So, for hard RT, those 65 us is the interesting number. How did you
create the system load? Typical tests contain some cache benchmarking
tool (I prefer calibrator: http://www.cwi.nl/~manegold/Calibrator) +
network load (e.g. ping -f) + hard disk or other persistent storage
access (e.g. dd if=<your-disk> of=/dev/null).
How much MHz does your board have, and to what can it be compared when
looking at other architectures. 65 us looks quite (too?) good for
low-end, but maybe the blackfin isn't actually low-end.
>
> That is, from the test result:
> HSS| min| 59| 31.746| 0.632
> HSS| avg| 599965| 33.365| 2.151
> HSS| max| 59| 53.339| 2.739
>
> Can I make the conclusion that the schedule latency is "determinative" and the system is "hard real-time"? If not,
> what is the expected test result? Xenomai is able to provide hard real-time, right?
Yes, Xenomai is a hard-RT system. But this doesn't depend on a specific
worst-case latency number, rather on the fact that a hardware-dependent
upper limit can be provided that is independent of the (here:) Linux load.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-04-12 7:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 8:32 [Xenomai-help] Questions porting existing rtai-24.1.12 app toxenomai Fillod Stephane
2006-04-04 14:24 ` [Xenomai-help] Questions porting existing rtai-24.1.12 app to xenomai (PART II) Randy Smith
2006-04-04 14:15 ` Philippe Gerum
2006-04-04 15:32 ` Randy Smith
2006-04-04 16:21 ` Philippe Gerum
2006-04-05 15:02 ` Randy Smith
2006-04-05 16:45 ` Philippe Gerum
2006-04-05 20:54 ` Randy Smith
2006-04-05 22:02 ` Philippe Gerum
2006-04-12 16:11 ` Randy Smith
2006-04-06 3:38 ` [Xenomai-help] question about the latency test running on Blackfin adam li
2006-04-06 7:05 ` Philippe Gerum
2006-04-07 12:27 ` adam li
2006-04-07 12:37 ` Philippe Gerum
2006-04-12 2:42 ` Li Yi
2006-04-12 7:46 ` Jan Kiszka [this message]
2006-04-12 12:28 ` adam li
2006-04-12 17:38 ` Jan Kiszka
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=443CB06C.2080202@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.org \
--cc=yi.li@domain.hid \
/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.