From: Tejun Heo <tj@kernel.org>
To: "chenxiang (M)" <chenxiang66@hisilicon.com>
Cc: martin.petersen@oracle.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH] scsi: ata: don't reset three times if device is offline for SAS host
Date: Tue, 13 Feb 2018 06:27:38 -0800 [thread overview]
Message-ID: <20180213142738.GJ695913@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <b3701a9b-3bf2-a979-cf75-c3dcdfaa1a89@hisilicon.com>
Hello,
On Tue, Feb 13, 2018 at 09:44:53AM +0800, chenxiang (M) wrote:
> For those drivers using libsas, i think they have the same issue.
> It takes about 1 minute to
> recover but actually device is gone, so this recover is useless for
> this scenario (when enter EH,
> all normal IOs are blocked actually, so it will cause normal IOs are
> blocked one more minute which
> user doesn't want to).
Right, it'd block other devices sharing the port. Doesn't sas map
each ata device to its own port tho?
> Actually in sas_ata_hard_reset, there are two situations returned
> -ENODEV which represent device is gone:
> - LLDD directly returns -ENODEV through lldd_I_T_nexus_reset;
> - It sends SMP DISCOVER to check local phy in smp_ata_check_ready,
> and find it is gone;
So, if there are real consequences, we can definitely add a way to
short-circuit the recovery logic but let's do that by adding proper
signaling rathr than testing for driver type.
Thanks.
--
tejun
prev parent reply other threads:[~2018-02-13 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 13:20 [PATCH] scsi: ata: don't reset three times if device is offline for SAS host chenxiang
2018-02-12 16:51 ` Tejun Heo
2018-02-13 1:44 ` chenxiang (M)
2018-02-13 14:27 ` Tejun Heo [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=20180213142738.GJ695913@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=chenxiang66@hisilicon.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.