From: Hannes Reinecke <hare@suse.de>
To: "Emmanuel Fusté" <emmanuel.fuste@laposte.net>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [AIC7xxx] tree things to report
Date: Tue, 29 May 2007 09:19:54 +0200 [thread overview]
Message-ID: <465BD41A.20708@suse.de> (raw)
In-Reply-To: <JIO6G3$AA5BDB4D4ABCE85E697964C3BA55EC36@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
Emmanuel Fusté wrote:
> Hello,
>
>> What you should do here is:
>>
>> - hook up a serial cable and re-route console messages to that
>> - Switch off syslog (as this might block if the SCSI bus frozen)
>> - Enable scsi debugging (Error, Timeout, Scan, and Midlayer is
>> sufficient) and start cdrwtools.
>> - Send me the log from the serial console.
>>
> Ok, I've got logs with netconsole after swapping my Ethernet
> card with another one.
Grand. Well done, son.
The logs have been very instructive.
Again we're hitting this 'two commands per lun' problem.
For historic reasons the aic7xxx and aic79xx driver accepted two
commands per luns, as they implemented their internal queueing and could
hold the second command on the queue.
With later versions I've removed this internal queueing and relied on
the block-layer for this.
But this also means we can only accept one command per lun.
Please try the attached patch and see if it helps.
James, I know that the aic7xxx has some 'next_queued_hscb' pointer which
might be utilized for this sort of thing. But I didn't really figure out
how this thing is supposed to work nor how we could utilize it.
So I figured that the added complexity is not really worth it.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
[-- Attachment #2: aic7xxx-allow-only-single-commands --]
[-- Type: text/plain, Size: 1322 bytes --]
Allow only a single command per lun for aic7xxx
With the conversion to use transport classes we also removed the
internal queueing from the driver. Hence the existing hack of
accepting two commands per lun and just holding this other one
internally is no longer valid.
Signed-off-by: Hannes Reinecke <hare@suse.de>
diff --git a/drivers/scsi/aic7xxx/aic79xx_osm.c b/drivers/scsi/aic7xxx/aic79xx_osm.c
index 6054881..df8a3b2 100644
--- a/drivers/scsi/aic7xxx/aic79xx_osm.c
+++ b/drivers/scsi/aic7xxx/aic79xx_osm.c
@@ -775,7 +775,7 @@ struct scsi_host_template aic79xx_driver
.can_queue = AHD_MAX_QUEUE,
.this_id = -1,
.max_sectors = 8192,
- .cmd_per_lun = 2,
+ .cmd_per_lun = 1,
.use_clustering = ENABLE_CLUSTERING,
.slave_alloc = ahd_linux_slave_alloc,
.slave_configure = ahd_linux_slave_configure,
diff --git a/drivers/scsi/aic7xxx/aic7xxx_osm.c b/drivers/scsi/aic7xxx/aic7xxx_osm.c
index 660f26e..e6b87b9 100644
--- a/drivers/scsi/aic7xxx/aic7xxx_osm.c
+++ b/drivers/scsi/aic7xxx/aic7xxx_osm.c
@@ -755,7 +755,7 @@ struct scsi_host_template aic7xxx_driver
.can_queue = AHC_MAX_QUEUE,
.this_id = -1,
.max_sectors = 8192,
- .cmd_per_lun = 2,
+ .cmd_per_lun = 1,
.use_clustering = ENABLE_CLUSTERING,
.slave_alloc = ahc_linux_slave_alloc,
.slave_configure = ahc_linux_slave_configure,
next prev parent reply other threads:[~2007-05-29 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 22:28 [AIC7xxx] tree things to report Emmanuel Fusté
2007-05-29 7:19 ` Hannes Reinecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 11:24 Emmanuel Fusté
2007-05-29 21:16 Emmanuel Fusté
2007-05-24 22:42 Emmanuel Fusté
2007-05-23 21:35 Emmanuel Fusté
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=465BD41A.20708@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=emmanuel.fuste@laposte.net \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).