public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Schumacher <matt.s@aptalaska.net>
To: linux-scsi@vger.kernel.org
Subject: new kernel = megaraid performance cut in half
Date: Tue, 14 May 2002 00:55:16 -0800	[thread overview]
Message-ID: <3CE0D0F4.3000601@aptalaska.net> (raw)

Hello,

I have a dell server that has a perc 3 DCL (megaraid) controller in it 
running redhat 7.2.  I was using the default kernel but I decided to 
upgrade to 2.4.18 to get the new VM code and for some quota fixes. 
Anyway, I compiled the kernel and the machine boots fine but my disk 
speed cut in half.

Is there anything I can do to resolve the speed issue so that I can 
continue using the 2.4.18 kernel?  This box is serving mail so 21MB sec 
on 3x10000rpm scsi3 disks in a raid 5 array is not acceptable.

Thanks for the help,

schu


[root@mail_test linux]# uname -a
Linux mail_test 2.4.18 #1 SMP Mon May 13 18:39:45 AKDT 2002 i686 unknown
[root@mail_test linux]# hdparm -t /dev/sda

/dev/sda:
  Timing buffered disk reads:  64 MB in  3.04 seconds = 21.05 MB/sec


Where on the default redhat kernel I get:

[root@mail_test root]# uname -a
Linux mail_test 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown
[root@mail_test root]# hdparm -t /dev/sda

/dev/sda:
  Timing buffered disk reads:  64 MB in  1.71 seconds = 37.43 MB/sec


             reply	other threads:[~2002-05-14  8:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  8:55 Matthew Schumacher [this message]
2002-05-14  9:21 ` new kernel = megaraid performance cut in half Alan Cox
2002-05-14  9:05   ` Matthew Schumacher
2002-05-14  9:30     ` Alan Cox
2002-05-14  9:48       ` Matthew Schumacher
2002-05-14 10:43         ` Alan Cox
2002-05-16  8:50 ` Mikael Abrahamsson
2002-05-16 16:39   ` Matthew Schumacher
2002-05-16 18:09     ` Alan Cox
2002-05-16 18:59       ` Matthew Schumacher

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=3CE0D0F4.3000601@aptalaska.net \
    --to=matt.s@aptalaska.net \
    --cc=linux-scsi@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