From: John Garry <john.garry@huawei.com>
To: Hannes Reinecke <hare@suse.de>,
JBottomley@odin.com, martin.petersen@oracle.com
Cc: linuxarm@huawei.com, zhangfei.gao@linaro.org,
xuwei5@hisilicon.com, john.garry2@mail.dcu.ie,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] hisi_sas: use slot abort in v2 hw
Date: Tue, 16 Feb 2016 16:58:50 +0000 [thread overview]
Message-ID: <56C3554A.9040106@huawei.com> (raw)
In-Reply-To: <56C34111.7080400@suse.de>
On 16/02/2016 15:32, Hannes Reinecke wrote:
> On 02/16/2016 01:22 PM, John Garry wrote:
>> When TRANS_TX_ERR_FRAME_TXED error occurs for
>> a command, the command should be re-attempted.
>>
>> Signed-off-by: John Garry <john.garry@huawei.com>
>> ---
>> drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 19 +++++++++++++++++--
>> 1 file changed, 17 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
>> index 58e1956..2bf93079b 100644
>> --- a/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
>> +++ b/drivers/scsi/hisi_sas/hisi_sas_v2_hw.c
>> @@ -1190,7 +1190,8 @@ static void sata_done_v2_hw(struct hisi_hba *hisi_hba, struct sas_task *task,
>> /* by default, task resp is complete */
>> static void slot_err_v2_hw(struct hisi_hba *hisi_hba,
>> struct sas_task *task,
>> - struct hisi_sas_slot *slot)
>> + struct hisi_sas_slot *slot,
>> + int *abort_slot)
>> {
>> struct task_status_struct *ts = &task->task_status;
>> struct hisi_sas_err_record_v2 *err_record = slot->status_buffer;
>> @@ -1299,6 +1300,13 @@ static void slot_err_v2_hw(struct hisi_hba *hisi_hba,
>> ts->stat = SAS_DATA_UNDERRUN;
>> break;
>> }
>> + case TRANS_TX_ERR_FRAME_TXED:
>> + {
>> + /* This will request a retry */
>> + ts->stat = SAS_QUEUE_FULL;
>> + ++(*abort_slot);
>> + break;
>> + }
>> case TRANS_TX_OPEN_FAIL_WITH_IT_NEXUS_LOSS:
>> case TRANS_TX_ERR_PHY_NOT_ENABLE:
>> case TRANS_TX_OPEN_CNX_ERR_BY_OTHER:
>> @@ -1491,11 +1499,17 @@ slot_complete_v2_hw(struct hisi_hba *hisi_hba, struct hisi_sas_slot *slot,
>>
>> if ((complete_hdr->dw0 & CMPLT_HDR_ERX_MSK) &&
>> (!(complete_hdr->dw0 & CMPLT_HDR_RSPNS_XFRD_MSK))) {
>> + int abort_slot = 0;
>> dev_dbg(dev, "%s slot %d has error info 0x%x\n",
>> __func__, slot->cmplt_queue_slot,
>> complete_hdr->dw0 & CMPLT_HDR_ERX_MSK);
>>
>> - slot_err_v2_hw(hisi_hba, task, slot);
>> + slot_err_v2_hw(hisi_hba, task, slot, &abort_slot);
>> + if (unlikely(abort_slot)) {
>> + queue_work(hisi_hba->wq, &slot->abort_slot);
>> + sts = ts->stat;
>> + goto out_1;
>> + }
>> goto out;
>> }
>>
> Again this weird 'abort_slot' pointer reshuffling.
> Care to clarify?
>
> Cheers,
>
> Hannes
>
Hopefully my explanation for patch #3 will help clarify here, as the
code is functionally the same.
Thanks,
John
next prev parent reply other threads:[~2016-02-16 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 12:22 [PATCH 0/6] hisi_sas: add abort and retry feature John Garry
2016-02-16 12:22 ` [PATCH 1/6] hisi_sas: add TMF_RESP_FUNC_SUCC check John Garry
2016-02-16 15:20 ` Hannes Reinecke
2016-02-16 12:22 ` [PATCH 2/6] hisi_sas: add hisi_sas_slot_abort() John Garry
2016-02-16 15:22 ` Hannes Reinecke
2016-02-16 15:41 ` John Garry
2016-02-18 9:30 ` John Garry
2016-02-16 12:22 ` [PATCH 3/6] hisi_sas: use slot abort in v1 hw John Garry
2016-02-16 15:31 ` Hannes Reinecke
2016-02-16 16:13 ` John Garry
2016-02-18 7:16 ` Hannes Reinecke
2016-02-18 9:52 ` John Garry
2016-02-16 12:22 ` [PATCH 4/6] hisi_sas: use slot abort in v2 hw John Garry
2016-02-16 15:32 ` Hannes Reinecke
2016-02-16 16:58 ` John Garry [this message]
2016-02-16 12:22 ` [PATCH 5/6] hisi_sas: add hisi_sas_slave_configure() John Garry
2016-02-16 15:33 ` Hannes Reinecke
2016-02-16 16:56 ` John Garry
2016-02-18 7:40 ` Hannes Reinecke
2016-02-18 10:12 ` John Garry
2016-02-18 10:30 ` Hannes Reinecke
2016-02-18 10:57 ` John Garry
2016-02-19 10:46 ` John Garry
2016-02-19 14:31 ` Hannes Reinecke
2016-02-22 10:02 ` John Garry
2016-02-16 12:22 ` [PATCH 6/6] hisi_sas: update driver version to 1.3 John Garry
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=56C3554A.9040106@huawei.com \
--to=john.garry@huawei.com \
--cc=JBottomley@odin.com \
--cc=hare@suse.de \
--cc=john.garry2@mail.dcu.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.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).