From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mikolaj Krzewicki <mkrzewicki@lycos.nl>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: benh performance problem
Date: Fri, 06 Feb 2004 16:14:36 +1100 [thread overview]
Message-ID: <1076044476.885.9.camel@gaston> (raw)
In-Reply-To: <40221664.70208@lycos.nl>
On Thu, 2004-02-05 at 21:09, Mikolaj Krzewicki wrote:
> the benchmark i used shows a speedup back to the values i'm used to.
> The benchmark itself is an octave script the execution time of which i
> tested with different kernels under similar circumstances, so here are
> the details:
>
> 2.6.1-benh1, HZ=1000: timing=36.5s
> 2.6.1-benh1, HZ=100 : timing=32s
>
> this is with X running and a lot more processes(not running).
> the weird thing is it executes slightly faster (on average) with
> pbbuttonsd off.
> The machine is g3 500 ibook, the octave script is:
>
> tic;
> a = abs(randn(1500, 1500)/10);
> b = a';
> c= a*b;
> a = reshape(b, 750, 3000);
> b = a';
> timing=toc;
>
> so lots of system calls and cache flushing is in order.
>
> Mikolaj.
Well, I don't knwo what the above means, I don't talk that language
anyway :)
The fact that pbbuttons makes a difference makes me think the
interrupt handling is taking way too much time on your setup,
and pbbuttons is loading the machine with PMU interrupts...
Not sure if I can fix any of this at this point without doing a
major rewrite of the exception handling code, I suspect those
CPUs don't like running in real mode and our exception handling
happens mostly in that mode in ppc32...
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-06 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 17:58 benh performance problem Mikolaj Krzewicki
2004-02-03 22:24 ` Benjamin Herrenschmidt
2004-02-05 21:50 ` Mikolaj Krzewicki
[not found] ` <40221664.70208@lycos.nl>
2004-02-06 5:14 ` Benjamin Herrenschmidt [this message]
2004-02-06 15:25 ` Hollis Blanchard
2004-02-07 21:16 ` Benjamin Herrenschmidt
2004-02-07 9:17 ` Gabriel Paubert
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=1076044476.885.9.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mkrzewicki@lycos.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).