From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: SPATZ1@t-online.de (Frank Schneider)
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: AIC + RAID1 error? (was: Re: aic7xxx errors)
Date: Fri, 07 Sep 2001 17:37:25 -0600 [thread overview]
Message-ID: <200109072337.f87NbPY92715@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Sat, 08 Sep 2001 00:51:32 +0200." <3B994F74.F97196BC@t-online.de>
>> You need to be running with aic7xxx=verbose for these messages to be
>> useful. In the 6.2.2 driver release I've turned these messages on
>> by default.
>
>Could you please shortly explain what this option does...(before it
>fills my logfiles with notes "succesfully wrote 1 Byte to disk abc"..:-)
It turns on some diagnostics regarding:
1) Card initialization
2) Transfer Negotiation (occurs with every check condition that occurs
prior to sending data, so while not rare, is
not a common occurrence).
3) Abort/Timeout processing
It should not fill your log file unless you have a timeout. This is
exactly the time you want it to fill your logs, so I can help diagnose
and fix your problem.
>> This is 8 times the tag load the old driver defaults to.
>
>Thats true, and e.g., my relatively new IBM-drives (DGHS18V, 2x
>DNES-309170W, DDRS-39130W, all Server-disks according to IBM) can only
>64...and the kernel complains, if i compile it with 255 and locks to
>64...
Its not really "complaining", its just telling you that it has determined
the proper setting for this device. There is an advantage to setting
your tag depth to the locked value - the SCSI layer cannot be told
dynamically to lower the tag depth, so there may be extra transactions
sitting in the driver queue for no real purpose - but its not that
big of a deal.
>as i have played with this feature a while ago, i did not realize a
>big performance-plus from 8 to 64, so i switched to 32...and i would go
>down to <8 if i where in doubt....
It all depends on your workload. If you run a news server or have lots
of concurrent active users on the machine, you are more likely to see
a difference.
--
Justin
next prev parent reply other threads:[~2001-09-07 23:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 6:21 aic7xxx errors Joseph Mathewson
2001-09-05 7:58 ` Olaf Zaplinski
2001-09-05 9:04 ` Frank Schneider
2001-09-05 10:27 ` Antonio Miguel Trindade
2001-09-05 10:44 ` Frank Schneider
2001-09-05 11:21 ` Thorsten Kranzkowski
2001-09-05 13:05 ` Frank Schneider
2001-09-07 20:32 ` AIC + RAID1 error? (was: Re: aic7xxx errors) Olaf Zaplinski
2001-09-07 22:32 ` Justin T. Gibbs
2001-09-07 22:51 ` Frank Schneider
2001-09-07 23:37 ` Justin T. Gibbs [this message]
2001-09-10 13:50 ` Olaf Zaplinski
2001-09-10 19:11 ` Frank Schneider
2001-09-10 22:29 ` Andreas Steinmetz
2001-09-10 22:42 ` Justin T. Gibbs
2001-09-10 22:55 ` Frank Schneider
2001-09-10 23:06 ` Justin T. Gibbs
2001-09-10 23:37 ` Andreas Steinmetz
2001-09-10 23:46 ` Justin T. Gibbs
2001-09-11 0:00 ` Andreas Steinmetz
2001-09-11 12:10 ` Frank Schneider
2001-09-11 16:51 ` Justin T. Gibbs
2001-09-10 23:05 ` Andreas Steinmetz
2001-09-10 22:46 ` Frank Schneider
2001-09-11 15:00 ` Olaf Zaplinski
2001-09-08 20:25 ` Frank Schneider
2001-09-08 22:07 ` Justin T. Gibbs
2001-09-05 20:23 ` aic7xxx errors Justin T. Gibbs
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=200109072337.f87NbPY92715@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=SPATZ1@t-online.de \
--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
all inboxes | Powered by JetHome®