From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Brian King <brking@linux.vnet.ibm.com>,
james.bottomley@hansenpartnership.com
Cc: brking@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] ibmvfc: add new fields for version 2 of several MADs
Date: Tue, 17 Nov 2020 16:28:41 -0800 [thread overview]
Message-ID: <d8fac4ba-e618-e941-c84a-67e1dc328325@linux.ibm.com> (raw)
In-Reply-To: <5b772ce2-3119-f05b-15d3-357729e46e70@linux.vnet.ibm.com>
On 11/17/20 2:06 PM, Brian King wrote:
> On 11/11/20 7:04 PM, Tyrel Datwyler wrote:
>> @@ -211,7 +214,9 @@ struct ibmvfc_npiv_login_resp {
>> __be64 capabilities;
>> #define IBMVFC_CAN_FLUSH_ON_HALT 0x08
>> #define IBMVFC_CAN_SUPPRESS_ABTS 0x10
>> -#define IBMVFC_CAN_SUPPORT_CHANNELS 0x20
>> +#define IBMVFC_MAD_VERSION_CAP 0x20
>> +#define IBMVFC_HANDLE_VF_WWPN 0x40
>> +#define IBMVFC_CAN_SUPPORT_CHANNELS 0x80
>> __be32 max_cmds;
>> __be32 scsi_id_sz;
>> __be64 max_dma_len;
>> @@ -293,6 +298,7 @@ struct ibmvfc_port_login {
>> __be32 reserved2;
>> struct ibmvfc_service_parms service_parms;
>> struct ibmvfc_service_parms service_parms_change;
>> + __be64 targetWWPN;
>
> For consistency, can you make this target_wwpn?
Sure thing.
>
>> __be64 reserved3[2];
>> } __packed __aligned(8);
>>
>> @@ -344,6 +350,7 @@ struct ibmvfc_process_login {
>> __be16 status;
>> __be16 error; /* also fc_reason */
>> __be32 reserved2;
>> + __be64 targetWWPN;
>
> For consistency, can you make this target_wwpn?
>
>> __be64 reserved3[2];
>> } __packed __aligned(8);
>>
>> @@ -378,6 +385,8 @@ struct ibmvfc_tmf {
>> __be32 cancel_key;
>> __be32 my_cancel_key;
>> __be32 pad;
>> + __be64 targetWWPN;
>
> For consistency, can you make this target_wwpn?
>
>> + __be64 taskTag;
>
> and make this task_tag.
Will do.
-Tyrel
>
>> __be64 reserved[2];
>> } __packed __aligned(8);
>>
>> @@ -474,9 +483,19 @@ struct ibmvfc_cmd {
>> __be64 correlation;
>> __be64 tgt_scsi_id;
>> __be64 tag;
>> - __be64 reserved3[2];
>> - struct ibmvfc_fcp_cmd_iu iu;
>> - struct ibmvfc_fcp_rsp rsp;
>> + __be64 targetWWPN;
>
> For consistency, can you make this target_wwpn?
>
>> + __be64 reserved3;
>> + union {
>> + struct {
>> + struct ibmvfc_fcp_cmd_iu iu;
>> + struct ibmvfc_fcp_rsp rsp;
>> + } v1;
>> + struct {
>> + __be64 reserved4;
>> + struct ibmvfc_fcp_cmd_iu iu;
>> + struct ibmvfc_fcp_rsp rsp;
>> + } v2;
>> + };
>> } __packed __aligned(8);
>>
>> struct ibmvfc_passthru_fc_iu {
>> @@ -503,6 +522,7 @@ struct ibmvfc_passthru_iu {
>> __be64 correlation;
>> __be64 scsi_id;
>> __be64 tag;
>> + __be64 targetWWPN;
>
> For consistency, can you make this target_wwpn?
>
>> __be64 reserved2[2];
>> } __packed __aligned(8);
>>
>>
>
>
next prev parent reply other threads:[~2020-11-18 0:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 1:04 [PATCH 1/6] ibmvfc: byte swap login_buf.resp values in attribute show functions Tyrel Datwyler
2020-11-12 1:04 ` [PATCH 2/6] ibmvfc: deduplicate common ibmvfc_cmd init code Tyrel Datwyler
2020-11-12 1:04 ` [PATCH 3/6] ibmvfc: add new fields for version 2 of several MADs Tyrel Datwyler
2020-11-17 22:06 ` Brian King
2020-11-18 0:28 ` Tyrel Datwyler [this message]
2020-11-12 1:04 ` [PATCH 4/6] ibmvfc: add FC payload retrieval routines for versioned vfcFrames Tyrel Datwyler
2020-11-17 22:14 ` Brian King
2020-11-17 22:21 ` Brian King
2020-11-18 0:39 ` Tyrel Datwyler
2020-11-18 0:34 ` Tyrel Datwyler
2020-11-12 1:04 ` [PATCH 5/6] ibmvfc: add support for targetWWPN field in v2 MADs and vfcFrame Tyrel Datwyler
2020-11-12 1:04 ` [PATCH 6/6] ibmvfc: advertise client support for targetWWPN using v2 commands Tyrel Datwyler
2020-11-17 22:23 ` Brian King
2020-11-12 9:37 ` [PATCH 1/6] ibmvfc: byte swap login_buf.resp values in attribute show functions Christoph Hellwig
2020-11-13 19:39 ` Tyrel Datwyler
2020-11-17 3:22 ` Martin K. Petersen
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=d8fac4ba-e618-e941-c84a-67e1dc328325@linux.ibm.com \
--to=tyreld@linux.ibm.com \
--cc=brking@linux.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).