From: Christoph Hellwig <hch@infradead.org>
To: mchristi@redhat.com
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [PATCH 3/5] target: call queue reset if supported
Date: Fri, 27 May 2016 01:22:15 -0700 [thread overview]
Message-ID: <20160527082215.GA31630@infradead.org> (raw)
In-Reply-To: <1464162903-14735-4-git-send-email-mchristi@redhat.com>
On Wed, May 25, 2016 at 02:55:01AM -0500, mchristi@redhat.com wrote:
> From: Mike Christie <mchristi@redhat.com>
>
> Instead of waiting for commands, map the lun reset operation
> to a queue reset.
>
> We do not check the result of blk_reset_queue because if
> it works then we need to wait for the bio/request completions
> and if it failed we might as wait and hope like we did before.
Please don't call into block device code from the file handler.
next prev parent reply other threads:[~2016-05-27 8:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 7:54 [PATCH 0/5] block/target queue/LUN reset support mchristi
2016-05-25 7:54 ` [PATCH 1/5] blk mq: take ref to q when running it mchristi
2016-05-25 15:53 ` Bart Van Assche
2016-05-25 19:15 ` Mike Christie
2016-05-25 19:20 ` Mike Christie
2016-05-25 7:55 ` [PATCH 2/5] block: add queue reset support mchristi
2016-05-25 16:13 ` Bart Van Assche
2016-05-25 19:16 ` Mike Christie
2016-05-25 7:55 ` [PATCH 3/5] target: call queue reset if supported mchristi
2016-05-27 8:22 ` Christoph Hellwig [this message]
2016-05-25 7:55 ` [PATCH 4/5] scsi: add new async device reset support mchristi
2016-05-27 8:23 ` Christoph Hellwig
2016-05-27 9:16 ` Hannes Reinecke
2016-05-30 6:27 ` Hannes Reinecke
2016-05-31 19:38 ` Mike Christie
2016-05-31 19:59 ` Mike Christie
2016-05-31 20:34 ` Mike Christie
2016-05-25 7:55 ` [PATCH 5/5] iscsi initiator: support eh_async_device_reset_handler mchristi
2016-05-30 6:37 ` [PATCH 0/5] block/target queue/LUN reset support Hannes Reinecke
2016-05-31 19:56 ` Mike Christie
2016-06-01 6:05 ` Hannes Reinecke
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=20160527082215.GA31630@infradead.org \
--to=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).