All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Sightler <ttsig@tuxyturvy.com>
To: Sylvain COUTANT <sylvain.coutant@illicom.com>
Cc: "'Matt Domsch'" <Matt_Domsch@dell.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: RE: High CPU usage (up to server hang) under heavy I/O load
Date: Fri, 13 Aug 2004 23:39:09 -0400	[thread overview]
Message-ID: <1092454748.3816.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20040813154737.7DCC12FC2C@illicom.com>

On Fri, 2004-08-13 at 11:46, Sylvain COUTANT wrote:
> Hello Matt,
> 
> > Which server please?
> 
> PE 2600 manufactured in June with latest PC BIOS and SCSI (PERC4/DI)
> BIOS/Firmware. We also tried downgrading to the previous release (as we have
> another PE2600 which runs fine with them) but it didn't do.

What driver are you using for the PERC?  We have a Dell 1750 with a
PERC/4Di which uses the megaraid driver under RHEL 3 and it has this
same problem, but only when writing to drives connected to PERC
controller.  The system also has a Qlogic 2312 card connected to a EMC
CX400 storage controller and performance to this device is fine, even if
I setup and LUN on a single ATA disk.

During heavy writes to the drives attached to the PERC4/Di the system
becomes practically unusable.  I've been wanting to try the 'megaraid2'
driver to see if this gets rid of the issue but I haven't been able to
try that yet.

We have some older systems with PERC2/DC cards which also use the
'megaraid' driver but they don't seem to experience this issue so I'm a
little suspicious that perhaps this driver simply doesn't work that well
with the newer megaraid-like controllers.

Later,
Tom



  reply	other threads:[~2004-08-14  3:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 14:01 High CPU usage (up to server hang) under heavy I/O load Sylvain COUTANT
2004-08-13 15:36 ` Matt Domsch
2004-08-13 15:46   ` Sylvain COUTANT
2004-08-14  3:39     ` Tom Sightler [this message]
2004-08-15  9:11       ` Lenar Lõhmus
2004-08-15 20:30       ` Sylvain COUTANT
2004-08-16 12:43         ` Matt Domsch
2004-08-13 16:20 ` Marcelo Tosatti
2004-08-13 17:53   ` Sylvain COUTANT
2004-08-16 10:11   ` Sylvain COUTANT
2004-08-16 11:49     ` Sylvain COUTANT
2004-08-13 22:16 ` Alan Cox
2004-08-16  9:13   ` Mark Watts
2004-08-16 10:57     ` Alan Cox
2004-08-16 12:10       ` Mark Watts

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=1092454748.3816.11.camel@localhost.localdomain \
    --to=ttsig@tuxyturvy.com \
    --cc=Matt_Domsch@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sylvain.coutant@illicom.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.