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: Thu, 16 May 2002 08:39:15 -0800	[thread overview]
Message-ID: <3CE3E0B3.4000108@aptalaska.net> (raw)
In-Reply-To: Pine.LNX.4.44.0205161049170.1330-100000@uplift.swm.pp.se

Mikael Abrahamsson wrote:
> On Tue, 14 May 2002, Matthew Schumacher wrote:
> 
> 
>>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.
> 
> 
> I am running 7.3 (upgraded from 7.2) and I feel that the 2.4.18 kernel
> with the new VM code is actually inferior to that of 2.4.9-31. I have lots
> of memory (1.2 gig) and lots of disk access, and I see more swap and worse
> interactive performance on 2.4.18 (redhat supplied kernel) as compared to 
> the redhat supplied 2.4.9-31 for 7.2.
> 


Hmm, the reason why I upgraded to 2.4.18 in the first place was to fix a 
bunch of problems with quota.  I wonder if 2.4.9-31 will work with the 
quotas correctly, I was on 2.4.7.

schu


  reply	other threads:[~2002-05-16 16:39 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
2002-05-14 10:43         ` Alan Cox
2002-05-16  8:50 ` Mikael Abrahamsson
2002-05-16 16:39   ` Matthew Schumacher [this message]
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=3CE3E0B3.4000108@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