From: zhangfei <zhangfei.gao@linaro.org>
To: John Garry <john.garry@huawei.com>,
jejb@linux.vnet.ibm.com, martin.petersen@oracle.com
Cc: linuxarm@huawei.com, xuwei5@hisilicon.com,
john.garry2@mail.dcu.ie, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] hisi_sas: add internal abort core code
Date: Sun, 21 Aug 2016 08:44:33 +0800 [thread overview]
Message-ID: <7a5a91f3-51bc-52ff-ded4-418133a67b4b@linaro.org> (raw)
In-Reply-To: <1470835205-65684-2-git-send-email-john.garry@huawei.com>
On 2016年08月10日 21:19, John Garry wrote:
> Add core code for internal abort functionality.
>
> The internal abort features allows the host controller
> to abort commands which are still active in the
> controller but have not yet been sent to the slave
> device.
>
> Typically a command only spends a relatively
> short time in the controller when compared to the
> amount of the time after it is sent to the slave
> device.
> Two modes of internal abort are supported:
> - device
> - individual command
>
> For device, when the internal abort is issued all
> commands in the host for that device are aborted.
> For a single command, only that command is aborted
> if it is still in the host.
>
> In HW the internal abort command is executed
> similar to any other sort of command, like SSP.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> drivers/scsi/hisi_sas/hisi_sas.h | 3 +
> drivers/scsi/hisi_sas/hisi_sas_main.c | 154 ++++++++++++++++++++++++++++++++++
> 2 files changed, 157 insertions(+)
>
> diff --git a/drivers/scsi/hisi_sas/hisi_sas.h b/drivers/scsi/hisi_sas/hisi_sas.h
> index 4731d32..4ae864d 100644
> --- a/drivers/scsi/hisi_sas/hisi_sas.h
> +++ b/drivers/scsi/hisi_sas/hisi_sas.h
> @@ -146,6 +146,9 @@ struct hisi_sas_hw {
> struct hisi_sas_slot *slot);
> int (*prep_stp)(struct hisi_hba *hisi_hba,
> struct hisi_sas_slot *slot);
> + int (*prep_abort)(struct hisi_hba *hisi_hba,
> + struct hisi_sas_slot *slot,
> + int device_id, int abort_flag, int tag_to_abort);
How about add comments to abort_flag and tag_to_abort.
As a result, not sure why differently calling in hisi_sas_abort_task
hisi_sas_internal_task_abort(hisi_hba, device, 1, tag);
hisi_sas_internal_task_abort(hisi_hba, device, 0, tag);
Thanks
next prev parent reply other threads:[~2016-08-21 0:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 13:19 [PATCH 0/8] hisi_sas internal abort support John Garry
2016-08-10 13:19 ` [PATCH 1/8] hisi_sas: add internal abort core code John Garry
2016-08-21 0:44 ` zhangfei [this message]
2016-08-22 7:50 ` John Garry
2016-08-10 13:19 ` [PATCH 2/8] hisi_sas: for internal abort in hisi_sas_dev_gone() John Garry
2016-08-10 13:20 ` [PATCH 3/8] hisi_sas: add internal abort to hisi_sas_abort_task() John Garry
2016-08-10 13:20 ` [PATCH 4/8] hisi_sas: add prep_abort_v2_hw() John Garry
2016-08-10 13:20 ` [PATCH 5/8] hisi_sas: add v2 hw slot complete internal abort support John Garry
2016-08-10 13:20 ` [PATCH 6/8] hisi_sas: fail tmf task prep when port detached John Garry
2016-08-10 13:20 ` [PATCH 7/8] hisi_sas: add TMF success check John Garry
2016-08-10 13:20 ` [PATCH 8/8] hisi_sas: update version to 1.6 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=7a5a91f3-51bc-52ff-ded4-418133a67b4b@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry2@mail.dcu.ie \
--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=xuwei5@hisilicon.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