From: Aaron Lehmann <aaronl@vitelus.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Complete I/O starvation with 3ware raid on 2.6
Date: Thu, 25 Sep 2003 03:15:46 -0700 [thread overview]
Message-ID: <20030925101546.GL22525@vitelus.com> (raw)
In-Reply-To: <3F72B1BC.7080405@cyberone.com.au>
On Thu, Sep 25, 2003 at 07:13:32PM +1000, Nick Piggin wrote:
> But the load average will be 11 because there are processes stuck in the
> kernel somewhere in D state. Have a look for them. They might be things
> like pdflush, kswapd, scsi_*, etc.
They're pdflush and kjournald. I don't have sysrq support compiled in
at the moment.
I've noticed the problem does not occur when the raid can absorb data
faster than the other drive can throw data at it. My naive mind is
pretty sure that this is just an issue of way too much being queued
for writing. If someone could tell me how to control this parameter,
I'd definately give it a try [tomorrow]. All I've found on my own is
#define TW_Q_LENGTH 256 in 3w-xxxx.h and am not sure if this is the
right thing to change or safe to change.
next prev parent reply other threads:[~2003-09-25 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 7:12 Complete I/O starvation with 3ware raid on 2.6 Aaron Lehmann
2003-09-25 7:43 ` Andrew Morton
2003-09-25 7:50 ` Aaron Lehmann
2003-09-25 8:02 ` Nick Piggin
2003-09-25 7:58 ` Aaron Lehmann
2003-09-25 8:10 ` Andrew Morton
2003-09-25 8:31 ` Aaron Lehmann
2003-09-25 9:13 ` Nick Piggin
2003-09-25 10:15 ` Aaron Lehmann [this message]
2003-09-25 10:25 ` Jens Axboe
2003-09-25 10:29 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2003-09-25 18:19 Adam Radford
2003-09-28 22:48 ` Aaron Lehmann
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=20030925101546.GL22525@vitelus.com \
--to=aaronl@vitelus.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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