From: James Smart <James.Smart@Emulex.Com>
To: ltuikov@yahoo.com
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] FC transport & lpfc : Avoid device offline cases by stalling aborts until device unblocked
Date: Tue, 07 Feb 2006 09:41:20 -0500 [thread overview]
Message-ID: <43E8B190.2030008@emulex.com> (raw)
In-Reply-To: <20060206191101.77227.qmail@web31809.mail.mud.yahoo.com>
> Is it possible that you add dev_loss_tmo to the scsi_dev timeout?
> Say scsi_dev->timeout = dev_loss_tmo + X seconds?
No. This would imply setting it in slave_configure, and which means commands
artificially have a longer timeout at all times, not just when we're in a
loss of connectivity.
I had considered having eh_timed_out return a time adder, so we timeout once
rather than periodically based on the io timeout value. However, the
calculations to come up with how much time remains on the dev_loss_tmo value,
coupled with adding a return value to this function, didn't seem worth it.
-- james s
prev parent reply other threads:[~2006-02-07 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 16:29 [PATCH] FC transport & lpfc : Avoid device offline cases by stalling aborts until device unblocked James Smart
2006-02-06 16:33 ` Christoph Hellwig
2006-02-06 19:11 ` Luben Tuikov
2006-02-07 14:41 ` James Smart [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=43E8B190.2030008@emulex.com \
--to=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.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).