From: Hannes Reinecke <hare@suse.de>
To: James Smart <james.smart@avagotech.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 02/17] lpfc: Fix the FLOGI discovery logic to comply with T11 standards
Date: Thu, 17 Dec 2015 09:10:10 +0100 [thread overview]
Message-ID: <56726DE2.4060001@suse.de> (raw)
In-Reply-To: <5671efb9.EUONcdfdiSClKLvo%james.smart@avagotech.com>
On 12/17/2015 12:11 AM, James Smart wrote:
>
> Fix the FLOGI discovery logic to comply with T11 standards
>
> We weren't properly setting fabric parameters, such as R_A_TOV and E_D_TOV,
> when we registered the vfi object in default configs and pt2pt configs.
> Revise to now pass service params with the values to the firmware and
> ensure they are reset on link bounce. Required reworking the call sequence
> in the discovery threads.
>
> Signed-off-by: Dick Kennedy <dick.kennedy@avagotech.com>
> Signed-off-by: James Smart <james.smart@avagotech.com>
> ---
> drivers/scsi/lpfc/lpfc_crtn.h | 1 +
> drivers/scsi/lpfc/lpfc_els.c | 342 +++++++++++++++++--------------------
> drivers/scsi/lpfc/lpfc_hbadisc.c | 12 +-
> drivers/scsi/lpfc/lpfc_nportdisc.c | 124 ++++++++------
> 4 files changed, 240 insertions(+), 239 deletions(-)
>
I hope you know what you're doing ...
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes 'who should be following T-11 more closely' Reinecke
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-12-17 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 23:11 [PATCH 02/17] lpfc: Fix the FLOGI discovery logic to comply with T11 standards James Smart
2015-12-17 8:10 ` Hannes Reinecke [this message]
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=56726DE2.4060001@suse.de \
--to=hare@suse.de \
--cc=james.smart@avagotech.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 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.