From: Andrew Morton <akpm@osdl.org>
To: Dave Olien <dmo@osdl.org>
Cc: linux-kernel@vger.kernel.org, piggin@cyberone.com.au
Subject: Re: [PATCH] 2.6.0-test11 DAC960 request queue per disk
Date: Mon, 15 Dec 2003 14:04:38 -0800 [thread overview]
Message-ID: <20031215140438.4371dbdb.akpm@osdl.org> (raw)
In-Reply-To: <20031215214053.GA3308@osdl.org>
Dave Olien <dmo@osdl.org> wrote:
>
>
> Here's a patch that changes the DAC960 driver from having one request
> queue for ALL disks on the controller, to having a request queue for
> each logical disk. This turns out to make little difference for deadline
> scheduler, nor for AS scheduler under light IO load. But under AS
> scheduler with heavy IO, it makes about a 40% difference on dbt2
> workload. Here are the measured numbers:
>
> The 2.6.0-test11-D kernel version includes this mutli-queue patch to the
> DAC960 driver.
>
> For non-cached dbt2 workload (heavy IO load)
>
> Scheduler kernel/driver NOTPM(bigger is better)
> AS 2.6.0-test11-D 1598
> AS 2.6.0-test11 973
> deadline 2.6.0-test11 1640
> deadline 2.6.0-test11-D 1645
>
> For cached dbt2 workload (lighter IO load)
>
> AS 2.6.0-test11-D 4993
> AS 2.6.-test6-mm4 4976, 4890, 4972
> deadline 2.6.0-test11-D 4998
Looks nice.
> Can this be included in 2.6.0? I know it's not a "critical patch"
> in the sense that something won't work without it. On the other hand,
> the change is isolated to a driver.
Let's queue it for 2.6.1 please. The default IO scheduler in 2.6.0 will
have some (known) efficiency problems anyway. (I thought those were fixed
in current -mm but we still seem to have tiobench randread problems).
prev parent reply other threads:[~2003-12-15 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 21:40 [PATCH] 2.6.0-test11 DAC960 request queue per disk Dave Olien
2003-12-15 22:04 ` Andrew Morton [this message]
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=20031215140438.4371dbdb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dmo@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