From: Hartmut Manz <manz@intes.de>
To: linux-kernel@vger.kernel.org
Subject: SCSI Controler SCRU32 becomes realy slow on the latest kernels
Date: Thu, 7 Dec 2006 14:28:44 +0100 [thread overview]
Message-ID: <200612071428.44850.manz@intes.de> (raw)
I am using here 2 machines with the ICP Vortex SCSI-Controler SCRU32 for some
years now.
After switching one machine from Debian 3.1 (sarge, with Kernel 2.6.8) to the
upcoming Debian 4.0 (etch with Kernel 2.6.17 or 2.6.18) I have noticed that
my scsi-devices become very slow while there is also a dramatical increase in
the sys time needed for I/O operations.
The machine is a dual processor Xeon system (2 * 2.2 GHz) with 2 GB memory.
The used scsi drives are seagate R10k and R15k disks.
i.e. reading 1 GB from the first SCSI drive takes about:
xen-1:/var/log# time dd if=/dev/sda bs=256k count=4000 of=/dev/null
4000+0 records in
4000+0 records out
1048576000 bytes (1.0 GB) copied, 55.3079 seconds, 19.0 MB/s
real 0m55.361s
user 0m0.368s
sys 0m49.107s
There are two strange things:
1. The transfer rate is only 19 MB/sec what is very low for this machine.
The expected value would be at least 50 MB/sec.
2. the system time is in the same range as the real time and thats
realy annoying, on the old kernel the system time for such an operatin
was about 7 sec.
Thanks for any help
Hartmut
--
-----------------------------------------------------------------------------
Hartmut Manz WWW: http://www.intes.de
INTES GmbH Phone: +49-711-78499-29
Schulze-Delitzsch-Str. 16 Fax: +49-711-78499-10
D-70565 Stuttgart E-mail: manz@intes.de
Gott spricht: Ich lasse dich nicht fallen und verlasse dich nicht.
------------------------------------------------------ Josua 1, 5b ---------
next reply other threads:[~2006-12-07 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 13:28 Hartmut Manz [this message]
2006-12-10 6:36 ` SCSI Controler SCRU32 becomes realy slow on the latest kernels Andrew Morton
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=200612071428.44850.manz@intes.de \
--to=manz@intes.de \
--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