From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: 3w-9xxx status in kernel
Date: Wed, 19 Apr 2006 14:02:13 +0000 (UTC) [thread overview]
Message-ID: <e25ft5$grl$1@news.cistron.nl> (raw)
In-Reply-To: e2558p$o5f$2@sea.gmane.org
In article <e2558p$o5f$2@sea.gmane.org>,
Martin Honermeyer <maze@strahlungsfrei.de> wrote:
>Hi,
>
>same problem over here. Why does the newest kernel contain an old version of
>the 3w-9xxx driver?
>
>We are having performance problems using a 9550SX controller. Read
>throughput (measured with hdparm) is worse than on a Desktop system. We are
>considering trying to replace it with the newest driver from 3ware.com.
The default settings for the 3w9xxx cards suck.
You need to make sure that the nr_requests (kernel request queue)
is at least twice the size of queue_depth (hardware requests queue).
Also the deadline or cfq i/o schedulers work a bit better for
database-like workloads.
Try something like this, replacing sda with the device name
of your 3ware controller.
# Limit queue depth somewhat
echo 128 > /sys/block/sda/device/queue_depth
# Increase nr_requests
echo 256 > /sys/block/sda/queue/nr_requests
# Don't use as for database-like loads
echo deadline > /sys/block/sda/queue/scheduler
CFQ seems to like larger nr_requests, so if you use CFQ, try 254
(maximum hardware size) for queue_depth and 512 or 1024 for nr_requests.
Oh, remember, if you have just created a RAID array on
the disks, wait with testing until the whole array has been
rebuild..
Mike.
prev parent reply other threads:[~2006-04-19 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 11:47 3w-9xxx status in kernel Stéphane Jourdois
2006-04-19 11:02 ` Martin Honermeyer
2006-04-19 13:36 ` "Stéphane (kwisatz) Jourdois"
2006-04-19 14:02 ` Miquel van Smoorenburg [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='e25ft5$grl$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox