From: David Chow <davidchow@shaolinmicro.com>
To: linux-kernel@vger.kernel.org, deanna_bonds@adaptec.com
Subject: complain about dpt_2o driver and CPU time
Date: Fri, 17 May 2002 13:16:32 +0800 [thread overview]
Message-ID: <3CE49230.40607@shaolinmicro.com> (raw)
Dear Deanna and others,
I am using the ASR2100 RAID card and running 2.4.17 Linux . It seems the
card is very slow in RAID5 computation. I use 5x18GB 10,000rpm seagate
drives. The card orginal comes with a 32MB ECC SD RAM as cache buffer. I
feel that the card is very slow, the test with Bonnie shows 1810KB/sec
with CPU load less than 2%. This shows the CPU time is idle, but the
load average go up to around 13-14 . This means the dpt_i2o driver is
probably not written very good in releasing the cpu time (call to
schedule()) on blocking calls, probably in some IO waiting routines(I am
not sure), or it is holding some big locks in a slow place. The CPU is
sitting there doing nothing, but this behaviour always block my NFS
clients ("server not responding, still trying") and the machine looks
like dead not even response to a console keyboard input. Can you tell me
about what is going on or who else is suffering from the same result? I
would like to do some improvement of the driver, or the card is really
that slow? My 10year old SCSI drive (no raid) runs 2200Kb/sec and is
even faster than this Ultra-160 SCSI i960 RAID with 32MB cache. If this
is the case, I will just throw it away and use my onboard Ultra-160
connector with software RAID which runs faster(at least). This is almost
unusable for even small workgroup server.
regards,
David
next reply other threads:[~2002-05-17 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 5:16 David Chow [this message]
2002-05-17 12:42 ` complain about dpt_2o driver and CPU time Alan Cox
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=3CE49230.40607@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=deanna_bonds@adaptec.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox