From: Grant Grundler <grundler@parisc-linux.org>
To: Steve Bromwich <hppa@fop.ns.ca>
Cc: Riccardo <rollei@tiscalinet.it>,
parisc linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] scsi problem on a scorpio (715)
Date: Wed, 7 Jan 2004 19:52:18 -0700 [thread overview]
Message-ID: <20040108025218.GA20732@colo.lackof.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0401072226130.5327@brain.fop.ns.ca>
On Wed, Jan 07, 2004 at 10:30:30PM -0400, Steve Bromwich wrote:
> Grant Grundler mentioned that "as of 5 years
> ago, HP-UX default was 8 for servers and 2 for workstations";
The drives shipped with workstations had "Write Cache Enable" (aka WCE)
turned on by default. Not good if you really care about your data.
But Tag queue depth of 2 works great because the drive will immediately
report "success" until it's on-board cache was full.
> as the 715
> is a workstation it might be worth trying setting tags to 2 and seeing
> what happens?
Unless performance is more important than strict correctness, I still
reccommend tag queue depth of 8 and disable "Write Cache" setting.
Reducing queue depth further typically only limits performance.
I suspect something else is wrong in Riccardo's case. But it wouldn't
hurt disable queue tags completely and see if that is at least stable.
root@debian:~# sginfo -c /dev/sda
Data from Caching Page
----------------------
Write Cache 0
Read Cache 1
Prefetch units 0
Demand Read Retention Priority 0
Demand Write Retention Priority 0
Disable Pre-fetch Transfer Length 65535
Minimum Pre-fetch 0
Maximum Pre-fetch 65535
Maximum Pre-fetch Ceiling 65535
hth,
grant
next prev parent reply other threads:[~2004-01-08 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 23:45 [parisc-linux] scsi problem on a scorpio (715) Riccardo
2004-01-08 2:30 ` Steve Bromwich
2004-01-08 2:52 ` Grant Grundler [this message]
2004-01-08 4:14 ` Carlos O'Donell
2004-01-08 4:31 ` John David Anglin
2004-01-08 5:10 ` Grant Grundler
2004-01-08 9:58 ` Riccardo
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=20040108025218.GA20732@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=hppa@fop.ns.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rollei@tiscalinet.it \
/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