From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, ohering@suse.com,
jbottomley@parallels.com, hch@infradead.org,
linux-scsi@vger.kernel.org
Subject: Drivers: scsi
Date: Wed, 24 Oct 2012 09:25:38 -0700 [thread overview]
Message-ID: <1351095938-12204-1-git-send-email-kys@microsoft.com> (raw)
When the low level driver returns SCSI_MLQUEUE_DEVICE_BUSY,
how is the command retried; I suspect the retry is done after some delay.
Is this delay programmable? If the device state changes,
can the low level driver notify upper layers that it can now handle
the command that it had failed earlier with SCSI_MLQUEUE_DEVICE_BUSY.
Regards,
K. Y
next reply other threads:[~2012-10-24 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 16:25 K. Y. Srinivasan [this message]
2012-10-24 22:25 ` Drivers: scsi James Bottomley
2012-10-24 22:34 ` KY Srinivasan
2012-11-03 16:40 K. Y. Srinivasan
2012-11-04 9:39 ` James Bottomley
2012-11-04 15:26 ` KY Srinivasan
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=1351095938-12204-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ohering@suse.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).