All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <kiszka@domain.hid>
To: Klaas Gadeyne <klaas.gadeyne@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] i386 2.4 backport performing (too?) well
Date: Fri, 02 Dec 2005 14:07:27 +0100	[thread overview]
Message-ID: <4390470F.8040503@domain.hid> (raw)
In-Reply-To: <Pine.LNX.4.63.0512021139500.2791@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Klaas Gadeyne wrote:
> With the arrival of the 2.4 i386 adeos ipipe patch for xenomai [1], I
> decided to try to compile xenomai-trunk for a 2.4 kernel. This worked
> flawlessly, and moreover, I got excellent latency results:
> 
> I used the "same" kernel config as for our 2.4.31 rtai3.0r5 kernel,
> which is based on Takis Issaris' liveCD config.
> 
> This resulted in a maximal latency of 30 usec after a run of over 100
> minutes under heavy load (tar and dd loops, compiling, keyboard
> interrupts and ping flood) [2].
> 
> For comparison, on the same hardware platform: - the RTAI lxrt-latency
> on rtai 3.0r5 (adeos oldgen r18c1
>   patch for 2.4.31 also) test reports 38 usec
> - the latency test of xenomai 2.01 running on a 2.6.14-ipipe-1.0-10
>   kernel resulted in a latency of 80 usec.
> 
> This seems too good to be true?  Can one simply compare the results of
> the former RTAI lxrt-latency test with the xenomai latency test?

Mmh, I tend to be sceptical as well, also remembering the results
Wolfgang posted about 2.6 vs. 2.4 on low-end PPC
(https://mail.gna.org/public/xenomai-core/2005-11/msg00131.html).

Well, such worst-case improvement may be real if and only if there is
less *kernel* code in hard-irq-off sections with 2.4. The complexity of
adeos/ipipe and xenomai isn't changed between both scenarios.

But I rather think that 2.4 just stresses the caches less than 2.6, thus
is may be more tricky to trigger the real worst-case path. So, what we
already saw with PPC: 2.4 and 2.6 may likely show similar RT
performances under Xenomai, but the overall system performance is much
better on low-end! However, I would be happy if this theory is too
pessimistic.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2005-12-02 13:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 12:15 [Xenomai-help] i386 2.4 backport performing (too?) well Klaas Gadeyne
2005-12-02 13:07 ` Jan Kiszka [this message]
2005-12-02 16:10   ` Wolfgang Grandegger
2005-12-02 16:34     ` Philippe Gerum
2005-12-02 16:54       ` Heikki Lindholm
2005-12-02 17:03       ` Wolfgang Grandegger
2005-12-02 13:23 ` Philippe Gerum
2005-12-05  9:09   ` Klaas Gadeyne
2005-12-05 10:08     ` 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=4390470F.8040503@domain.hid \
    --to=kiszka@domain.hid \
    --cc=klaas.gadeyne@domain.hid \
    --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.