From: Nick Piggin <piggin@cyberone.com.au>
To: Aaron Lehmann <aaronl@vitelus.com>
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 18:02:06 +1000 [thread overview]
Message-ID: <3F72A0FE.6030201@cyberone.com.au> (raw)
In-Reply-To: <20030925075016.GG22525@vitelus.com>
Aaron Lehmann wrote:
>On Thu, Sep 25, 2003 at 12:43:01AM -0700, Andrew Morton wrote:
>
>>An update to the 3ware driver was merged yesterday. Have you used earlier
>>2.5 kernels?
>>
>
>Unfortunately not. I copied a day-old CVS tree to the machine but
>decided to update before compiling to get the latest-and-greatest. I
>did notice the 3ware updates.
>
>I rebooted with the deadline scheduler. It definately isn't helping.
>
OK, one problem is most likely something I added a month or so ago: a
new process is now assumed to be not a good anticipate candidate. This
solved some guy's obscure problem, but a lot of programs that benefit from
anticipation (ls, gcc, vi startup, cat, etc) are only going to submit a
few requests in their life, so they lose most of the gains. I have some
automatic thingy I'm testing at the moment.
The other problem could well be a big TCQ depth. AS helps with this, but
it can't do a really good job. Try a TCQ depth of max 4.
next prev parent reply other threads:[~2003-09-25 8:02 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 [this message]
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
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=3F72A0FE.6030201@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=aaronl@vitelus.com \
--cc=akpm@osdl.org \
--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.