From: Wenchao Hao <haowenchao@huawei.com>
To: <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Mike Christie <michael.christie@oracle.com>,
Lee Duncan <lduncan@suse.com>
Cc: Wu Bo <wubo40@huawei.com>, Feilong Lin <linfeilong@huawei.com>,
<zhangjian013@huawei.com>
Subject: [REQUEST DISCUSS]: speed up SCSI error handle for host with massive devices
Date: Tue, 29 Mar 2022 17:06:30 +0800 [thread overview]
Message-ID: <71e09bb4-ff0a-23fe-38b4-fe6425670efa@huawei.com> (raw)
SCSI timeout would call scsi_eh_scmd_add() on some conditions, host
would be set
to SHOST_RECOVERY state. Once host enter SHOST_RECOVERY, IOs submitted
to all
devices in this host would not succeed until the scsi_error_handler()
finished.
The scsi_error_handler() might takes long time to be done, it's
unbearable when
host has massive devices.
I want to ask is anyone applying another error handler flow to address this
phenomenon?
I think we can move some operations(like scsi get sense, scsi send startunit
and scsi device reset) out of scsi_unjam_host(), to perform these operations
without setting host to SHOST_RECOVERY? It would reduce the time of
block the
whole host.
Waiting for your discussion.
next reply other threads:[~2022-03-29 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:06 Wenchao Hao [this message]
2022-03-29 10:56 ` [REQUEST DISCUSS]: speed up SCSI error handle for host with massive devices Steffen Maier
2022-03-29 12:40 ` Wenchao Hao
2022-03-29 18:56 ` Hannes Reinecke
2022-03-30 9:11 ` Wenchao Hao
2022-03-30 9:32 ` Hannes Reinecke
2022-03-30 10:59 ` Wenchao Hao
2022-04-03 17:14 ` Mike Christie
2022-04-03 17:17 ` Mike Christie
2022-04-04 5:28 ` Hannes Reinecke
2022-04-04 7:40 ` Christoph Hellwig
2022-04-06 9:40 ` Wenchao Hao
2023-10-12 14:50 ` Hannes Reinecke
2023-10-12 16:09 ` Wenchao Hao
2022-04-06 10:32 ` Wenchao Hao
2022-04-06 9:40 ` Wenchao Hao
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=71e09bb4-ff0a-23fe-38b4-fe6425670efa@huawei.com \
--to=haowenchao@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=lduncan@suse.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=wubo40@huawei.com \
--cc=zhangjian013@huawei.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