From: Konstantin Shelekhin <k.shelekhin@yadro.com>
To: Mike Christie <michael.christie@oracle.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<target-devel@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
John Youn <John.Youn@synopsys.com>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] target: Implement TMR_ABORT_TASK_SET
Date: Wed, 20 Jul 2022 18:41:10 +0300 [thread overview]
Message-ID: <YtggwBMKgIJqN4mT@yadro.com> (raw)
In-Reply-To: <74bf1df3-a466-9d78-1a25-7425c89b9fa3@oracle.com>
On Tue, Jul 19, 2022 at 10:56:07AM -0500, Mike Christie wrote:
> «Внимание! Данное письмо от внешнего адресата!»
>
> On 7/18/22 9:07 PM, Thinh Nguyen wrote:
> > Task ABORT TASK SET function is required by SCSI transport protocol
>
> What OS is using this and how do they use it? For the latter, does the
> OS try an abort for each cmd first, then try an abort task set if the
> aborts fail (does fail mean get a response that indicates failure and
> also does a timeout count)? Or does it start with the abort task set?
AIX IIRC. However, this feature also requires valid bits in one of the
VPD pages.
next prev parent reply other threads:[~2022-07-20 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 2:06 [PATCH v2 0/4] target: Updates related to UASP Thinh Nguyen
2022-07-19 2:07 ` [PATCH v2 1/4] target: Handle MI_REPORT_SUPPORTED_OPERATION_CODES Thinh Nguyen
2022-07-19 13:31 ` Konstantin Shelekhin
2022-07-19 22:44 ` Thinh Nguyen
2022-07-19 15:31 ` Mike Christie
2022-07-19 22:48 ` Thinh Nguyen
2022-07-19 2:07 ` [PATCH v2 2/4] target: Implement TMR_ABORT_TASK_SET Thinh Nguyen
2022-07-19 15:56 ` Mike Christie
2022-07-19 23:05 ` Thinh Nguyen
2022-07-20 15:41 ` Konstantin Shelekhin [this message]
2022-07-19 2:07 ` [PATCH v2 3/4] target: Properly set Sense Data Length of CHECK CONDITION Thinh Nguyen
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=YtggwBMKgIJqN4mT@yadro.com \
--to=k.shelekhin@yadro.com \
--cc=John.Youn@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.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 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.