From: James Smart <James.Smart@Emulex.Com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andreas Herrmann <AHERRMAN@de.ibm.com>,
James Bottomley <jejb@steeleye.com>,
Linux SCSI <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fc transport: new attributes for NPIV
Date: Mon, 09 Jan 2006 14:04:39 -0500 [thread overview]
Message-ID: <43C2B3C7.4010506@emulex.com> (raw)
In-Reply-To: <20060109180513.GA4286@infradead.org>
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
next prev parent reply other threads:[~2006-01-09 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFE227A343.800436AC-ON412570ED.0055DD4F-412570ED.00560A75@de.ibm.com>
2006-01-05 17:28 ` [PATCH] fc transport: new attributes for NPIV James Smart
2006-01-09 18:05 ` Christoph Hellwig
2006-01-09 19:04 ` James Smart [this message]
2006-01-09 23:09 ` Andreas Herrmann
2006-01-10 18:00 ` James Smart
2006-01-09 23:59 ` Andreas Herrmann
2006-01-10 18:11 ` James Smart
2006-01-05 9:01 Andreas Herrmann
2006-01-05 14:08 ` James Smart
2006-01-05 15:51 ` Andreas Herrmann
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=43C2B3C7.4010506@emulex.com \
--to=james.smart@emulex.com \
--cc=AHERRMAN@de.ibm.com \
--cc=hch@infradead.org \
--cc=jejb@steeleye.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.