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: Re: new kernel = megaraid performance cut in half
Date: Tue, 14 May 2002 01:48:43 -0800	[thread overview]
Message-ID: <3CE0DD7B.9090201@aptalaska.net> (raw)
In-Reply-To: E177YdO-0007VV-00@the-village.bc.nu

Alan,

FYI,

[root@mail_test root]# uname -a
Linux mail_test 2.4.18-4smp #1 SMP Thu May 2 18:32:34 EDT 2002 i686 unknown
[root@mail_test root]# hdparm -t /dev/sda

/dev/sda:
  Timing buffered disk reads:  64 MB in  1.22 seconds = 52.46 MB/sec
[root@mail_test root]# hdparm -t /dev/sda

So the redhat 2.4.18 kernel reads disk almost 2.5 times better on my 
system.... sounds like something that would be handy in a stable kernel 
release.

Thanks for you help,

schu


Alan Cox wrote:
>>I am running exactly 1g of ram in the machine.  Is there a way to apply 
>>those patches manually or should I get the kernel-2.4.18-4.i686.rpm from 
>>here: http://rhn.redhat.com/errata/RHBA-2002-085.html.
> 
> 
> Your best bet is probably to grab the RH errata kernel. If you get the
> source rpm that also includes the patches for some controllers to do
> I/O from all of memory.
> 
> Hopefully that restores the speed




  reply	other threads:[~2002-05-14  9:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  8:55 new kernel = megaraid performance cut in half Matthew Schumacher
2002-05-14  9:21 ` Alan Cox
2002-05-14  9:05   ` Matthew Schumacher
2002-05-14  9:30     ` Alan Cox
2002-05-14  9:48       ` Matthew Schumacher [this message]
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=3CE0DD7B.9090201@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