From: Mike Anderson <andmike@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: randy.dunlap@verizon.net, linux-scsi@vger.kernel.org, mjacob@feral.com
Subject: Re: [PATCH] reduce stack in qlogicfc.c
Date: Wed, 12 Mar 2003 01:38:26 -0800 [thread overview]
Message-ID: <20030312093826.GA5322@beaverton.ibm.com> (raw)
In-Reply-To: <20030312005220.637494ae.akpm@digeo.com>
Andrew Morton [akpm@digeo.com] wrote:
> Mike Anderson <andmike@us.ibm.com> wrote:
> >
> > Randy.Dunlap [randy.dunlap@verizon.net] wrote:
> > > Can anyone suggest way(s) to have the isp2x00_make_portdb() function
> > > called over and over again until it gets its job done?
> > > Or does anyone even still use this driver?
> >
> > We have been using the Feral as it covers both Qlogic SCSI and FC cards
> > (both 2200 and 2300 series, the qlogicfc only handles 2200). I believe
> > Andrew Morton is carrying the driver in the mm series of patches.
> >
>
> Does it work? After an initial spurt of not-so-hot testing reports
> everything went quiet and I'd assumed people had given up on it
> for the while.
No we have not given up. It works, but we still have the outstanding
issue that we can overdrive the card do to the combination of can_queue,
device queue_depth and the ring size allocated for the card. A longer
term fix is need for this which Matthew is aware of. In the short term
some adjustments of these values will reduce the number of requeues that
are happening and also keep the SCSI error handler for firing for
timeouts.
-andmike
--
Michael Anderson
andmike@us.ibm.com
prev parent reply other threads:[~2003-03-12 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 6:11 [PATCH] reduce stack in qlogicfc.c Randy.Dunlap
2003-03-12 7:20 ` Mike Anderson
2003-03-12 8:52 ` Andrew Morton
2003-03-12 9:38 ` Mike Anderson [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=20030312093826.GA5322@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mjacob@feral.com \
--cc=randy.dunlap@verizon.net \
/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