Sebastian,
"not portable" isn't the right way to describe it. It's not a
chip-architecture issue, but rather that some oem platforms have
side-band management that overrides anything that could have been done
in the os, and in ways that may not be easy to communicate back to the
driver. FAWN - true Brocade only - but that is the 70+% market share
of the FC switches. The current implementation already doesn't work many
situations - so there's no clear winner for having it work everywhere.
Given the inability for it always to work, the decision was to deprecate
the attribute.
-- james
On 12/28/2016 10:38 AM, Sebastian Herbszt wrote:
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
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
