From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: FCP target reset
Date: Tue, 4 Aug 2009 10:46:38 +0200 [thread overview]
Message-ID: <20090804084637.GA3835@schmichrtp.de.ibm.com> (raw)
In-Reply-To: <4A774AC8.8080805@emulex.com>
On Mon, Aug 03, 2009 at 04:38:32PM -0400, James Smart wrote:
> Just because a newer rev of the spec doesn't do something does not mean
> that all the targets/environments stopped using it... Target Reset was a
> mandatory item for FCP-2 compliance, which is what most of the stuff in
> the field is at. So, I recommend that the header be updated with the
> older definition - It can be flagged any way you desire (/* Deprecated as
> of FCP-3 */).
>
> As for use in LLD's - there's nothing else (TMF-wise) that works at the
> I_T nexus level to map to the shost eh_target_reset_handler. Thus, I'd
> continue to use it for the entrypoint. You can always choose to not
> implement the entry point, but my recommendation is to support it if
> possible. It's much better than having to resort to a "bus" or "adapter"
> reset after a lun reset fails.
I agree that it makes sense to keep this. My question resulted partly
from the confusion about the removal of this function in recent specs.
Here is a patch to add the target reset flag to the FCP header file to
use it in zfcp (and other SCSI FC drivers).
Christof
---
SCSI: Add target reset flag to FCP header file
From: Christof Schmitt <christof.schmitt@de.ibm.com>
While the target reset task management function has been deprecated in
newer specs, it is still in use by SCSI FC drivers and there is no real
replacement. Add the target reset flag to the FCP header file to allow
use of this definition in SCSI FC drivers.
Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com>
---
include/scsi/fc/fc_fcp.h | 2 ++
1 file changed, 2 insertions(+)
--- a/include/scsi/fc/fc_fcp.h 2009-03-24 13:50:59.000000000 +0100
+++ b/include/scsi/fc/fc_fcp.h 2009-08-04 10:28:50.000000000 +0200
@@ -84,6 +84,8 @@ struct fcp_cmnd32 {
*/
#define FCP_TMF_CLR_ACA 0x40 /* clear ACA condition */
#define FCP_TMF_LUN_RESET 0x10 /* logical unit reset task management */
+#define FCP_TMF_TGT_RESET 0x20 /* target reset task management,
+ deprecated as of FCP-3 */
#define FCP_TMF_CLR_TASK_SET 0x04 /* clear task set */
#define FCP_TMF_ABT_TASK_SET 0x02 /* abort task set */
next prev parent reply other threads:[~2009-08-04 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 16:23 FCP target reset Christof Schmitt
2009-08-03 20:38 ` James Smart
2009-08-04 8:46 ` Christof Schmitt [this message]
2009-08-04 14:38 ` Douglas Gilbert
2009-08-04 16:03 ` James Smart
2009-08-04 16:20 ` James Bottomley
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=20090804084637.GA3835@schmichrtp.de.ibm.com \
--to=christof.schmitt@de.ibm.com \
--cc=James.Smart@Emulex.Com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox