From: James Bottomley <James.Bottomley@steeleye.com>
To: "Smart, James" <James.Smart@Emulex.com>
Cc: Linux SCSI Reflector <linux-scsi@vger.kernel.org>
Subject: Re: Transport affected timeouts...
Date: 16 Apr 2004 14:24:22 -0500 [thread overview]
Message-ID: <1082143462.1807.31.camel@mulgrave> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF2802C0169E@xbl.ma.emulex.com>
On Fri, 2004-04-16 at 10:40, Smart, James wrote:
> One issue that we're wrestling with in our driver is timeout values. In the
> past, we've encountered large configurations where the timeouts from the
> midlayer are insufficient. In general - we'd like the scsi host to be able
> to add a transport/topology increment time to the base timeout values. The
> methodology would have to be dynamic as it may change as link connectivity
> changes.
>
> Obviously, an hba driver mucking with the timeout values handed to it is
> frowned upon. Is there a recommendation on how we should handle this ?
There's no currently agreed upon framework, but would
http://www-124.ibm.com/storageio/ipr/patch-2.6.5-sd_timeout_mod
Do for what you want?
James
next prev parent reply other threads:[~2004-04-16 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 15:40 Transport affected timeouts Smart, James
2004-04-16 19:24 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 19:39 Smart, James
2004-04-16 19:46 ` James Bottomley
2004-04-16 20:13 Smart, James
2004-04-21 16:53 Smart, James
2004-04-21 19:20 ` James Bottomley
2004-04-22 16:28 Smart, James
2004-04-22 18:14 ` Brian King
2004-04-22 18:54 Smart, James
2004-04-22 19:02 ` James Bottomley
2004-04-22 19:09 ` Brian King
2004-04-22 21:36 Smart, James
2004-04-22 21:45 ` Brian King
2004-05-03 15:49 ` Brian King
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=1082143462.1807.31.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=James.Smart@Emulex.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.