All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Fillod Stephane <stephane.fillod@domain.hid>
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 15:09:48 +0200	[thread overview]
Message-ID: <4356459C.30306@domain.hid> (raw)
In-Reply-To: <1CFEB358338412458B21FAA0D78FE86D4F0E31@domain.hid>

Fillod Stephane wrote:
> Philippe Gerum wrote:
> [..]
> 
> http://download.gna.org/adeos/patches/v2.6/adeos/ppc/adeos-ipipe-2.6.13-
> ppc-1.0-02.patch
> 
> Here is the result of tests with version 1.0-02 on e500:
> 
> load: ~1 minute ping -f, one run of calibrator chewing 64MiB.
> 
> $ cat /proc/ipipe/version
> 1.0-02
> 
> 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
> RTD|        4620|        4740|        8190|           0    1.0-02
> 
> 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
> RTS|       -6150|       -4183|       12480|       0|    00:03:38 1.0-02
> 
> 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
> RTS|       -5700|       -3750|       11280|       0|    00:06:05 1.0-02
> 
> It looks like the char vs. long in the 1.0-0[12] patch was not the
> culprit,

The last significant change between -00 and -01 is actually the one related to 
the fork pressure (others are cosmetic ones aimed at better sharing stuff with 
the blackfin port). The patch below against -02 removes it.

--- 2.6.13/arch/ppc/kernel/entry.S~	2005-10-18 18:42:09.000000000 +0200
+++ 2.6.13/arch/ppc/kernel/entry.S	2005-10-19 15:07:54.000000000 +0200
@@ -316,10 +316,8 @@

  	.globl	ret_from_fork
  ret_from_fork:
-	STALL_ROOT_COND
  	REST_NVGPRS(r1)
  	bl	schedule_tail
-	UNSTALL_ROOT_COND
  	li	r3,0
  	b	ret_from_syscall

> at least not on e500. I'll do the bench again on 1.0-00. Man, if only we
> had that automated benchmark suite...
> 

Indeed... The positive thing being that, we now have the ultimate proof of its 
usefulness :o>

-- 

Philippe.


  reply	other threads:[~2005-10-19 13:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19 11:52 [Xenomai-core] Testing the adeos-ipipe-2.6.13-ppc-1.0-00.patch Fillod Stephane
2005-10-19 13:09 ` 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 10:05 Fillod Stephane
2005-10-19 11:00 ` Philippe Gerum
2005-10-19 11:21   ` 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=4356459C.30306@domain.hid \
    --to=rpm@xenomai.org \
    --cc=stephane.fillod@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.