From: luojiaxing <luojiaxing@huawei.com>
To: <martin.petersen@oracle.com>, <jejb@linux.ibm.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<john.garry@huawei.com>, <yanaijie@huawei.com>,
<chenxiang66@hisilicon.com>, <linuxarm@huawei.com>
Subject: Re: [PATCH v2 0/2] scsi: libsas: An improvement on error handle and tidy-up
Date: Sat, 25 Jul 2020 16:59:53 +0800 [thread overview]
Message-ID: <90974ce1-abd4-7b6d-c4cf-08e4a922c6fd@huawei.com> (raw)
In-Reply-To: <1595665131-24543-1-git-send-email-luojiaxing@huawei.com>
sorry，I missed Martin's e-mail "Re: [PATCH v1 0/2] scsi: libsas: An
improvement on error handle and tidy-up" here. Please ignore this set of
patches.
On 2020/7/25 16:18, Luo Jiaxing wrote:
> This patch introduces an improvement to reduce error handle time and a
> tidy-up, including:
> - postreset() is deleted from sas_sata_ops.
> - Do not perform hard reset and delayed retry on a removed SATA disk. This
> can effectively reduce the error handle duration of hot unplug a SATA disk
> with traffic(reduce about 30s depending on the delay setting of libata).
>
> Both John garry and Jason Yan participated in the review of the solution
> and provided good suggestions during the development.
>
> Change since v1:
> - Removed an unnecessary tag from subject.
>
> Luo Jiaxing (2):
> scsi: libsas: delete postreset at sas_sata_ops
> scsi: libsas: check link status at ATA prereset() ops
>
> drivers/scsi/libsas/sas_ata.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2020-07-25 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 8:18 [PATCH v2 0/2] scsi: libsas: An improvement on error handle and tidy-up Luo Jiaxing
2020-07-25 8:18 ` [PATCH v2 1/2] scsi: libsas: delete postreset at sas_sata_ops Luo Jiaxing
2020-07-25 8:18 ` [PATCH v2 2/2] scsi: libsas: check link status at ATA prereset() ops Luo Jiaxing
2020-07-25 8:59 ` luojiaxing [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=90974ce1-abd4-7b6d-c4cf-08e4a922c6fd@huawei.com \
--to=luojiaxing@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=yanaijie@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;
as well as URLs for NNTP newsgroup(s).