From: yangxingui <yangxingui@huawei.com>
To: John Garry <john.g.garry@oracle.com>, <liyihang9@huawei.com>,
<yanaijie@huawei.com>
Cc: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <prime.zeng@huawei.com>,
<liuyonglong@huawei.com>, <kangfenglong@huawei.com>,
<liyangyang20@huawei.com>, <f.fangjian@huawei.com>,
<xiabing14@h-partners.com>
Subject: Re: [PATCH v3 1/3] scsi: hisi_sas: Enable force phy when SATA disk directly connected
Date: Tue, 11 Mar 2025 09:53:15 +0800 [thread overview]
Message-ID: <b6dcc1e5-7f43-ec10-fbd9-48def2f6517f@huawei.com> (raw)
In-Reply-To: <1fe3bb6b-1f7a-4188-83a3-f4c62e2a963d@oracle.com>
On 2025/3/11 1:45, John Garry wrote:
>>> Sure, but I am just trying to keep this simple. If you deform and
>>> reform the port - and so lose and find the disk (which does the itct
>>> config) - will that solve the problem?
>>>
>> We found that we need to perform lose and find for all devices on the
>> port including the local phy and the remote phy. This process still
>> requires traversing the phy information corresponding to all devices
>> to reset and it is also necessary to consider that there is a race
>> between device removal and the current process. it looks similar to
>> solution of update port id directly. And there will be the problem
>> mentioned above. e.g, during error handling, the recovery state will
>> last for more than 15 seconds, affecting the performance of other
>> disks on the same host.
>
> How do you even detect the port id inconsistency for the device attached
> at the remote phy? For this series, you could detect it at the phy
> up/down handler for the directly attached device - how would it be
> triggered for the remote phy?
When the hardware port ID of the EXP is detected to have changed, the
link reset is performed on the local phy of EXP in sequence, which will
not trigger the lose and find process of the EXP device, and it will not
trigger the lose and find process of the disks connected to the remote
phy. Therefore, it is necessary to lose and found all devices separately
to update the device's port id in itct.
local phy0 --------------------------- disk0
local phy1 --------------------------- disk1
local phy2 --------------------------- disk2
local phy3 --------------------------- disk3
_________
local phy4 --------| |-------- disk4
| |
local phy5 --------| |-------- disk5
| |
local phy6 --------| EXP |-------- disk6
| |
local phy7 --------| |-------- disk7
|_________|
Thanks,
Xingui
.
next prev parent reply other threads:[~2025-03-11 1:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:05 [PATCH v3 0/3] scsi: hisi_sas: Fixed IO error caused by port id not updated Xingui Yang
2025-02-20 13:05 ` [PATCH v3 1/3] scsi: hisi_sas: Enable force phy when SATA disk directly connected Xingui Yang
2025-02-20 17:35 ` John Garry
2025-02-21 1:59 ` yangxingui
2025-02-24 8:29 ` John Garry
2025-02-24 9:36 ` yangxingui
2025-02-24 12:21 ` John Garry
2025-02-24 13:12 ` yangxingui
2025-02-24 17:34 ` John Garry
2025-02-25 1:48 ` yangxingui
2025-02-25 8:19 ` John Garry
2025-02-25 9:35 ` yangxingui
2025-02-26 8:57 ` John Garry
2025-02-27 8:33 ` yangxingui
2025-03-04 9:48 ` John Garry
2025-03-05 8:16 ` yangxingui
2025-03-05 16:15 ` John Garry
2025-03-06 1:44 ` yangxingui
2025-03-10 13:09 ` yangxingui
2025-03-10 17:45 ` John Garry
2025-03-11 1:53 ` yangxingui [this message]
2025-03-12 9:44 ` yangxingui
2025-03-12 11:19 ` John Garry
2025-02-20 13:05 ` [PATCH v3 2/3] scsi: libsas: Move sas_put_device() to libsas.h Xingui Yang
2025-02-21 2:36 ` Jason Yan
2025-02-20 13:05 ` [PATCH v3 3/3] scsi: hisi_sas: Fixed IO error caused by port id not updated Xingui Yang
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=b6dcc1e5-7f43-ec10-fbd9-48def2f6517f@huawei.com \
--to=yangxingui@huawei.com \
--cc=f.fangjian@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=john.g.garry@oracle.com \
--cc=kangfenglong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=liyangyang20@huawei.com \
--cc=liyihang9@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=prime.zeng@huawei.com \
--cc=xiabing14@h-partners.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
all inboxes | Powered by JetHome®