From: Philippe Gerum <rpm@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Testing the adeos-ipipe-2.6.13-ppc-1.0-00.patch
Date: Wed, 19 Oct 2005 13:21:26 +0200 [thread overview]
Message-ID: <43562C36.1090609@domain.hid> (raw)
In-Reply-To: <4356274A.5010004@domain.hid>
Philippe Gerum wrote:
> Fillod Stephane wrote:
>
>> Wolfgang Grandegger wrote:
>> [...]
>>
>>>> Load for klatency/latency was ping flooding on FCC (piece of cake),
>>>> and cache calibrator. IMHO, we can do nastier.
>>>
>>>
>>> You mean the cache calibrator from http://monetdb.cwi.nl/Calibrator/? I
>>> tried it on my Ocotea board and it increased the max latency for 25 to
>>> 30 us.
>>
>>
>>
>> Yes, that very one. In this case, it has been used as a cache trashing
>> load generator. But IMHO, this Calibrator should be better used in the
>> Benchmarking Plan to get L1/L2/RAM access latency figures (w/o RT
>> running),
>> and offer one more correlation against RT latency results.
>>
>> We can afford a better cache trashing load generator. Earlier this year,
>> I proposed flushy(tm) [1], but as Philippe suggested, we can do better.
>> Flushy should be rewritten as an ADEOS layer, inserted just in front
>> of Xenomai in the pipeline. This way, we would be sure the caches
>> are dead cold when Xenomai enter its domain. Using tools like OProfile,
>> it should be possible then to track cache misses, and fix them by
>> prefetching, where available.
>>
>> [1] http://rtai.dk/cgi-bin/gratiswiki.pl?Latency_Killer (bottom of page)
>>
>>
>> Here is the result of my 1.0-01 tests on e500:
>>
>> $ cat /proc/ipipe/version
>> 1.0-01
>>
>> SWITCH without load:
>> RTH| lat min| lat avg| lat max| lost
>> RTD| 3660| 3690| 8070| 0 1.0-00
>> RTD| 4620| 4740| 8730| 0 1.0-01
>>
>> KLATENCY with load:
>> RTH|-----lat min|-----lat avg|-----lat max|-overrun|
>> RTS| -7350| -5715| 6420| 0| 00:03:17 1.0-00
>> RTS| -6150| -4384| 12180| 0| 00:03:13 1.0-01
>>
>> LATENCY with load:
>> == Sampling period: 100 us
>> RTH|-----lat min|-----lat avg|-----lat max|-overrun|
>> RTS| -6930| -4260| 8700| 0| 00:08:06 1.0-00
>> RTS| -5670| -4620| 12930| 0| 00:12:39 1.0-01
>>
>> That's weird. Figures are worse, but since the load (ping -f +
>> calibrator)
>> was executed manually, it may not be the same.
>>
>
> Ok, I now suspect that another change regarding the size of the
> interrupt counters made this worse. I'm going to revert it and upload
> -02, just to make sure.
>
http://download.gna.org/adeos/patches/v2.6/adeos/ppc/adeos-ipipe-2.6.13-ppc-1.0-02.patch
--
Philippe.
next prev parent reply other threads:[~2005-10-19 11:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 10:05 [Xenomai-core] Testing the adeos-ipipe-2.6.13-ppc-1.0-00.patch Fillod Stephane
2005-10-19 11:00 ` Philippe Gerum
2005-10-19 11:21 ` Philippe Gerum [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-19 13:54 Fillod Stephane
2005-10-19 14:00 ` Philippe Gerum
2005-10-19 11:52 Fillod Stephane
2005-10-19 13:09 ` Philippe Gerum
2005-10-17 15:42 Fillod Stephane
2005-10-17 20:02 ` Philippe Gerum
2005-10-18 9:59 ` Wolfgang Grandegger
2005-10-19 9:11 ` Wolfgang Grandegger
2005-10-15 18:52 Wolfgang Grandegger
2005-10-15 19:17 ` Heikki Lindholm
2005-10-17 7:47 ` Wolfgang Grandegger
2005-10-17 8:00 ` Philippe Gerum
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=43562C36.1090609@domain.hid \
--to=rpm@xenomai.org \
--cc=xenomai@xenomai.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 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.