From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Putrid Elevator Behavior 2.4.18/19
Date: Wed, 20 Mar 2002 15:20:08 -0700 [thread overview]
Message-ID: <20020320152008.A19978@vger.timpanogas.org> (raw)
In-Reply-To: <20020320120455.A19074@vger.timpanogas.org> <20020320220241.GC29857@matchmail.com>
On Wed, Mar 20, 2002 at 02:02:41PM -0800, Mike Fedyk wrote:
> On Wed, Mar 20, 2002 at 12:04:55PM -0700, Jeff V. Merkey wrote:
> >
> >
> >
> > Jens/Linux,
> >
> > The elevator code is malfunctioning in 2.4.18/19-pre when we start
> > reaching the upward limits with multiple 3Ware adapters
> > running together. We started seeing the problem when we went to
> > 64 K aligned writes with sustained > 200 MB/S writes to
> > multiple 3Ware adapters.
> >
> > We have verified that the 3Ware adapters are not holding the request
> > off, but that one of the requests is getting severely starved and
> > does not get posted to the 3Ware adapters until thousands of IOs
> > have gone before it.
> >
>
> This elevator starvation problem has been identified and a patch already
> merged into 2.4.19-pre2.
>
> Can you verify the affects it produces for your workload?
I will comply. I tested with pre-3 patches and still saw this problem??
Let me go and check the patches I applied to verify, I may not have
applied the correct patch.
Jeff
next prev parent reply other threads:[~2002-03-20 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 19:04 Putrid Elevator Behavior 2.4.18/19 Jeff V. Merkey
2002-03-20 22:02 ` Mike Fedyk
2002-03-20 22:20 ` Jeff V. Merkey [this message]
2002-03-20 22:25 ` Jeff V. Merkey
2002-03-21 1:22 ` Andrew Morton
2002-03-21 6:45 ` Jeff V. Merkey
2002-03-26 1:16 ` Jeff V. Merkey
2002-03-26 1:42 ` Mike Fedyk
2002-03-26 17:03 ` Jeff V. Merkey
2002-03-27 7:03 ` Jens Axboe
2002-03-27 23:20 ` Jeff V. Merkey
2002-03-26 1:45 ` David Rees
2002-03-26 1:57 ` Mike Fedyk
2002-03-26 17:00 ` Jeff V. Merkey
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=20020320152008.A19978@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.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.