From: Mark Watts <m.watts@eris.qinetiq.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: High CPU usage (up to server hang) under heavy I/O load
Date: Mon, 16 Aug 2004 10:13:13 +0100 [thread overview]
Message-ID: <200408161013.13829.m.watts@eris.qinetiq.com> (raw)
In-Reply-To: <1092435364.24960.35.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Is your raid controller 64bit capable ? If you can I'd also go to a 2.6
> kernel for anything > 1Gb, and definitely > 4Gb of RAM. The differences
> are astounding although if your PCI I/O hardware cant do 64bit access
> your box will suck whatever kernel 8)
Would this also mean that if I stick a 64bit SATA raid card (a 3Ware 8506-4LP
in this case) into a 32bit pci slot, then I/O is always going to suck badly?
... cos I do, and I/O sucks :)
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services group
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBIHqpBn4EFUVUIO0RAr4HAKCXDnm8YM2f7jY9awix/0KVyoUvYwCeJdmU
+gatlxR+IHurHnTPXDDITqk=
=2Rrq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-08-16 9:14 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
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 [this message]
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=200408161013.13829.m.watts@eris.qinetiq.com \
--to=m.watts@eris.qinetiq.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.