Christoph Hellwig wrote:
Actually I think even for Xen-like virtualization it makes most sense that
most domains wouldn't see the Scsi_Host for the phyisical port so this solution
looks most sane to me. The long name for the physical names sounds fine to me
as well, much better than un-understandable three-latter acronyms :)
So my grind is just with the "physical_port_xxx" reference. It's too logical
of a name for someone uninitiated with NPIV. How do they know the difference
between physical_port_name and port_name, especially where the predominance of
configs will always have the same values in both attributes ? Choosing
something "physical" always seem like a better choice.
I should have known better on the abbreviation.... :)
Having made this argument - I then said - why not use the name from the
standards, "permanent_port_xxx". But, when I look at this, it's not much
different. Permanent vs Physical ? at least the abbreviation gave it some
separation. Bah Humbug. My preference is still "permanent" over "physical"
as it tracks the standards name.
-- james
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
