From: Wolfgang Grandegger <wg@grandegger.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-rt-users@vger.kernel.org, John Stultz <johnstul@us.ibm.com>
Subject: Re: High latencies on MPC5200 with patch-2.6.24-rc5-rt1
Date: Thu, 10 Jan 2008 14:17:02 +0100 [thread overview]
Message-ID: <47861ACE.9060301@grandegger.com> (raw)
In-Reply-To: <20080110000124.GW3177@pengutronix.de>
Hi Robert,
Robert Schwebel wrote:
> Wolfgang,
>
> On Wed, Jan 09, 2008 at 11:51:07PM +0100, Robert Schwebel wrote:
>> Throwing in the versions from 2.6.23.3-rt5 doesn't help, the effect
>> stays the same. So I assume it is a side effect.
>
> Can you test the following patch by John Stulz (thanks to John for the quick
> help on irc!), which fixes the issues on my board:
>
> ----------8<----------
> Index: linux-2.6.24-rc5/arch/powerpc/kernel/time.c
> ===================================================================
> --- linux-2.6.24-rc5.orig/arch/powerpc/kernel/time.c
> +++ linux-2.6.24-rc5/arch/powerpc/kernel/time.c
> @@ -773,7 +773,7 @@ void update_vsyscall(struct timespec *wa
> stamp_xsec = (u64) xtime.tv_nsec * XSEC_PER_SEC;
> do_div(stamp_xsec, 1000000000);
> stamp_xsec += (u64) xtime.tv_sec * XSEC_PER_SEC;
> - update_gtod(clock->cycle_last, stamp_xsec, t2x);
> + update_gtod(clock->cycle_last-clock->cycle_accumulated, stamp_xsec, t2x);
> }
>
> void update_vsyscall_tz(void)
> ----------8<----------
>
> With this patch ontop of 2.6.24-rc5-rt1 plus the board support patches
> for the phyCORE-MPC5200B-tiny, I get this result from cyclictest, again
> under "(while true; do hackbench 10; done) &" load:
>
> T: 0 ( 867) P:80 I: 10000 C: 105002 Min: 31 Act: 48 Avg: 51 Max: 92
Unfortunately, it doesn't really help on my Icecube board.
bash-3.00# ./cyclictest -n -p80 -i1000
129.85 93.18 38.05 4/45 6354
130.41 162.23 83.05 3/49 8395
T: 0 ( 4621) P:80 I:1000 C: 477097 Min: 25 Act: 64 Avg: 67 Max:
286
bash-3.00# ./hackbench 10
Time: 95.402
Could you run your cyclictest much longer?
And hackbench takes ages, already without running cyclictest:
bash-3.00# time ./hackbench 10
Time: 83.157
real 1m23.935s
user 0m5.692s
sys 1m18.240s
With a standard non-rt kernel it just takes 10 seconds.
bash-3.00# time ./hackbench 10
Time: 9.690
real 0m10.343s
user 0m0.404s
sys 0m9.928s
Is this the normal/expected behavior under -rt?
Wolfgang.
next prev parent reply other threads:[~2008-01-10 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 10:13 High latencies on MPC5200 with patch-2.6.24-rc5-rt1 Wolfgang Grandegger
2008-01-08 15:49 ` Robert Schwebel
2008-01-08 16:41 ` Wolfgang Grandegger
2008-01-08 20:40 ` Robert Schwebel
2008-01-08 21:25 ` Juergen Beisert
2008-01-09 9:03 ` Robert Schwebel
2008-01-09 9:50 ` Wolfgang Grandegger
2008-01-09 14:08 ` Robert Schwebel
2008-01-09 22:51 ` Robert Schwebel
2008-01-10 0:01 ` Robert Schwebel
2008-01-10 13:17 ` Wolfgang Grandegger [this message]
2008-01-10 14:35 ` Robert Schwebel
2008-01-10 16:23 ` Robert Schwebel
2008-01-10 21:27 ` Robert Schwebel
2008-01-10 21:49 ` Wolfgang Grandegger
2008-01-10 15:48 ` Juergen Beisert
2008-01-11 9:22 ` Wolfgang Grandegger
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=47861ACE.9060301@grandegger.com \
--to=wg@grandegger.com \
--cc=johnstul@us.ibm.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
--cc=tglx@linutronix.de \
/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.