From: Mikolaj Krzewicki <mkrzewicki@lycos.nl>
To: linuxppc-dev@lists.linuxppc.org
Subject: benh performance problem
Date: Tue, 03 Feb 2004 18:58:16 +0100 [thread overview]
Message-ID: <401FE138.8080807@lycos.nl> (raw)
hi all,
starting 2.6.0-test9-benh3 i noticed an increased system overhead on my
ibook 500. Each process eats much more cpu time than in 2.4 or even
vanilla 2.6.
gkrellm takes 1% instead of 0.1, xmms 5% instead of ~1% and so on.
I benchmarked the lot with octave and it indeed runs ~10% slower on the
benh kernels.
I would use vanilla 2.6.1 but it won't sleep/wake correctly (at all).
All pre-2.6.0-test9-benh3 kernels worked fast but would't sleep/wake either.
I tried to isolate the patch responsible but failed.
Has anybody come across similar behaviour?
greetings, M.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-02-03 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 17:58 Mikolaj Krzewicki [this message]
2004-02-03 22:24 ` benh performance problem Benjamin Herrenschmidt
2004-02-05 21:50 ` Mikolaj Krzewicki
[not found] ` <40221664.70208@lycos.nl>
2004-02-06 5:14 ` Benjamin Herrenschmidt
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=401FE138.8080807@lycos.nl \
--to=mkrzewicki@lycos.nl \
--cc=linuxppc-dev@lists.linuxppc.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.