From: Jes Sorensen <jes@wildopensource.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Jeremy Higdon <jeremy@sgi.com>,
Linux-SCSI <linux-scsi@vger.kernel.org>,
jbarnes@sgi.com, mdr@sgi.com
Subject: Re: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b6).
Date: 25 Nov 2003 03:21:22 -0500 [thread overview]
Message-ID: <yq0ptfgj1tp.fsf@wildopensource.com> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B0598D30@AVEXCH02.qlogic.org>
>>>>> "Andrew" == Andrew Vasquez <andrew.vasquez@qlogic.com> writes:
Andrew> The (additional-)firmware options, perhaps a subset, seem like
Andrew> a (possibily) reasonable thing to force at the driver level.
Andrew> But, on the otherhand, the retry, delay and timer counts tend
Andrew> to be very customer specific based on topology and storage.
Andrew> Additionally, the driver already exports via module parameters
Andrew> several of the more important driver retry and timer counts,
Andrew> i.e. port_down_try_count, link_down_timeout, retry_count (try
Andrew> modinfo for a full list). A user can use these facilities to
Andrew> perform any fine-tuning.
Andrew,
I would be a nice feature if all these tuning parameters were exported
via sysfs in 2.6 allowing users to modify them at runtime without
having to reload the module every time. It would be very useful to
test tuning parameters etc.
Cheers,
Jes
next prev parent reply other threads:[~2003-11-25 8:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 17:37 [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b6) Andrew Vasquez
2003-11-25 1:22 ` Jeremy Higdon
2003-11-25 8:18 ` Christoph Hellwig
2003-11-25 8:21 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 18:22 Andrew Vasquez
2003-12-02 18:10 Andrew Vasquez
2003-12-01 23:21 Andrew Vasquez
2003-12-02 2:02 ` Jeremy Higdon
2003-12-02 10:01 ` Andrew Vasquez
2003-12-02 9:36 ` Jeremy Higdon
2003-12-02 3:22 ` Jeremy Higdon
2003-12-02 10:15 ` Andrew Vasquez
2003-12-02 9:50 ` Jeremy Higdon
2003-11-25 19:29 Andrew Vasquez
2003-11-25 23:31 ` Jeremy Higdon
2003-11-27 1:20 ` Jeremy Higdon
2003-11-19 23:38 Andrew Vasquez
2003-11-19 23:03 Andrew Vasquez
2003-11-19 23:18 ` Matthew Wilcox
2003-11-20 9:19 ` Jes Sorensen
2003-11-21 8:43 ` Jeremy Higdon
2003-11-06 19:33 Andrew Vasquez
2003-11-07 9:39 ` Christoph Hellwig
2003-11-06 17:45 Andrew Vasquez
2003-11-06 17:59 ` Arjan van de Ven
2003-11-07 9:37 ` Christoph Hellwig
2003-11-06 17:11 Andrew Vasquez
2003-11-06 17:14 ` Jens Axboe
2003-11-06 17:43 ` Arjan van de Ven
2003-11-06 17:50 ` Jens Axboe
2003-11-06 17:55 ` Arjan van de Ven
2003-11-06 17:58 ` Jens Axboe
2003-11-06 17:02 Andrew Vasquez
2003-11-06 17:53 ` Matthew Wilcox
2003-11-07 9:58 ` Christoph Hellwig
2003-11-07 9:33 ` Christoph Hellwig
2003-11-05 18:39 Andrew Vasquez
2003-11-06 9:17 ` Jens Axboe
2003-11-05 1:15 Andrew Vasquez
2003-11-05 9:17 ` Mike Anderson
2003-11-06 9:36 ` Christoph Hellwig
2003-11-06 10:51 ` Christoph Hellwig
2003-11-10 14:00 ` Jes Sorensen
[not found] ` <20031114115847.GA32664@lst.de>
2003-11-17 12:18 ` Christoph Hellwig
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=yq0ptfgj1tp.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=andrew.vasquez@qlogic.com \
--cc=jbarnes@sgi.com \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.com \
/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).