From: "Albrecht Dreß" <ad@mpifr-bonn.mpg.de>
To: "Timothy A. Seufert" <tas@mindspring.com>
Cc: LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Strange PMAC IDE performance problem
Date: Tue, 05 Jan 1999 12:33:25 +0100 [thread overview]
Message-ID: <3691F885.77C7D466@mpifr-bonn.mpg.de> (raw)
In-Reply-To: v04011700b2b76717bf6b@[209.86.156.101]
Timothy A. Seufert wrote:
[snip]
> Needless to say, the IDE performance figures are far less than those drives
> are capable of! Under MacOS they benchmark much higher (for example, the
[snip]
I can confirm this behaviour on my PowerBook G3/300 with almost the same rate
under 2.1.130 (the disk is an IBM DYLA 28100). Furthermore, the whole system
nearly freezes under heavy io load (I simply used a program which writes and
reads blocks of data to/from the disk using read and write calls in a loop;
during the run the reaction to console input or a "cat" needs several seconds,
etc.). I posted this problem several times, but got no reaction, so I am glad
that I am not alone ... :-(
The problem might be connected to LOADS of "Bogus interrupts" from do_IRQ in
arch/ppc/kernel/irq.c (try "dmesg" and do a "cat /proc/interrupts" before and
after your test; you will see the increase in the "BAD" line).
I think that this is a serious problem, as it makes the machine nearly unusable
fore some applications. Hope it will get fixed ;-)
Yours, Albrecht.
--
+-----------------------------------------------------------------------------+
| Dr.-Ing. Albrecht Dre\3 ---- |
| Max-Planck-Institut f"ur Radioastronomie |\ / /o o\ |
| Technische Abt. Optische Interferometrie | \ / | / | |
| Auf dem H"ugel 69 | \ | \ ---/ |
| D-53121 Bonn (Germany) ------------+------+------------------- |
| | / | |
| Phone (+49) 228 525 319 | / / |
| Fax (+49) 228 525 411 |/ / |
| Mail ad@mpifr-bonn.mpg.de |
+-------------- electrical engineers do it with less resistance --------------+
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-05 11:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-05 8:52 Strange PMAC IDE performance problem Timothy A. Seufert
1999-01-05 11:33 ` Albrecht Dreß [this message]
1999-01-05 17:52 ` Marcus H. Mendenhall
1999-01-05 18:49 ` Timothy A. Seufert
1999-01-05 22:48 ` Benjamin Herrenschmidt
1999-01-06 5:56 ` Dan Malek
1999-01-06 9:59 ` Benjamin Herrenschmidt
1999-01-06 9:23 ` Albrecht Dreß
1999-01-06 10:02 ` Benjamin Herrenschmidt
1999-01-06 23:22 ` Paul Mackerras
1999-01-07 9:11 ` Benjamin Herrenschmidt
1999-01-05 22:39 ` Paul Mackerras
1999-01-06 6:01 ` Paul Mackerras
1999-01-06 11:51 ` Benjamin Herrenschmidt
1999-01-06 16:02 ` Great IDE perf (WAS: Strange PMAC IDE performance) Benjamin Herrenschmidt
1999-01-07 11:12 ` Timothy A. Seufert
1999-01-07 11:32 ` Paul Mackerras
1999-01-07 18:59 ` Timothy A. Seufert
1999-01-07 11:59 ` Benjamin Herrenschmidt
1999-01-07 18:59 ` Timothy A. Seufert
1999-01-07 20:15 ` Benjamin Herrenschmidt
1999-01-08 2:06 ` Paul Mackerras
1999-01-08 3:30 ` Benjamin Herrenschmidt
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=3691F885.77C7D466@mpifr-bonn.mpg.de \
--to=ad@mpifr-bonn.mpg.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/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).