From: Mike Christie <michaelc@cs.wisc.edu>
To: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, axboe@suse.de
Subject: [PATCH 0/2] blk request timeout handler
Date: Tue, 25 Jul 2006 05:51:07 -0400 [thread overview]
Message-ID: <44C5E98B.4040903@cs.wisc.edu> (raw)
Sorry if this is a duplicate, I had some trouble with my mailer in the
middle if sending the patches.
The following patches move the scsi command timeout code from the scsi
layer to the block layer. I originally did them so request based
multipath could reuse the code, but the code can be used by anyone so I
thought I should send it seperately.
I have tested the normal and error paths with iscsi and am in the middle
of testing the libata error paths. The latter needs more care since it
is the only strategy handler user. I have also converted all the
timeout_per_command users but some of the LLDs still need a "#include
blkdev.h".
So the patches are not ready for mergingm but I wanted to get feedback
on the scsi timer code and if it was accpetable or was it not so nice?
And I wanted to see if these patches were ok alone or if all the scsi eh
needed to be moved at the same time. These patches do not move the
quiesce, abort or reset code.
reply other threads:[~2006-07-25 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44C5E98B.4040903@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox