From: Sebastian Herbszt <herbszt@gmx.de>
To: James Smart <james.smart@broadcom.com>
Cc: linux-scsi@vger.kernel.org, Hannes Reinecke <hare@suse.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [PATCH v2 03/11] lpfc: Deprecate lpfc_soft_wwn parameter
Date: Wed, 28 Dec 2016 19:38:32 +0100 [thread overview]
Message-ID: <20161228193832.00000ba9@gmx.de> (raw)
In-Reply-To: <1a6d026b-f896-84a9-2c81-9a3bfebd01dd@broadcom.com>
James Smart wrote:
> I competes, without reasonable solutions to resolve which should be
> what at what time, with things like fabric-assigned wwn's as well as
> platform-oem name assignments via platform mechanisms. Too many
> admin planes competing.
>
> -- james
FA-WWN seems to be fabric (and Brocade?) only and "platform mechanisms"
are likely not portable. Soft wwn is a simple and flexible solution
which works in fabric and loop configurations and is platform and
server vendor agnostic. It already works with existing HBAs on x86 and
should also work on PowerPC or SPARC systems.
It is useful for initiators (hardware independence/mobility) and
targets (transparent failover/floating wwn).
Therefore I like to ask you to revert this patch and not introduce this
functional regression.
Sebastian
next prev parent reply other threads:[~2016-12-28 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 23:07 [PATCH v2 03/11] lpfc: Deprecate lpfc_soft_wwn parameter James Smart
2016-12-20 13:36 ` Hannes Reinecke
2016-12-22 22:00 ` Sebastian Herbszt
2016-12-23 16:44 ` James Smart
2016-12-28 18:38 ` Sebastian Herbszt [this message]
2016-12-29 4:45 ` James Smart
2016-12-29 7:41 ` Christoph Hellwig
2016-12-29 18:17 ` James Smart
2016-12-29 23:31 ` Sebastian Herbszt
2016-12-30 15:21 ` James Smart
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=20161228193832.00000ba9@gmx.de \
--to=herbszt@gmx.de \
--cc=hare@suse.com \
--cc=james.smart@broadcom.com \
--cc=linux-scsi@vger.kernel.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).