From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: linux-scsi@vger.kernel.org, duane.grigsby@qlogic.com
Subject: Re: [PATCH] FC Transport support for vports based on NPIV
Date: Mon, 14 May 2007 14:12:40 +0200 [thread overview]
Message-ID: <20070514121239.GA23620@schmichrtp> (raw)
In-Reply-To: <1176408091.19824.20.camel@localhost.localdomain>
James,
i try to understand what the introduction of the vports means for zfcp, since
this driver also supports NPIV. The documentation for the fc transport class
describes a driver that would fully control the adapter and the creation of
virtual address. Since you mentioned Xen, i assume that this could be a dom0.
With zfcp, the hardware FCP adapter does NPIV and only hands out the virtual
address to individual Linux instances. zfcp gets the assigned virtual address
for the Linux instance. This address is used for allocating the scsi_host
structure. Basically, the whole system uses NPIV, but each Linux only uses one
assigned virtual WWPN.
My current understanding is that the vports introduced in the fc transport
class do not affect the Linux systems that only use one virtual address. To
map this to Xen, the dom0 would use the vports to show all virtual address, and
each domU would use the assigned virtual address without showing the vport in
sysfs. Is this correct?
Christof
next prev parent reply other threads:[~2007-05-14 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 20:01 [PATCH] FC Transport support for vports based on NPIV James Smart
2007-05-12 15:02 ` Christoph Hellwig
2007-05-14 12:12 ` Christof Schmitt [this message]
2007-05-14 15:56 ` ` James Smart
2007-05-14 15:57 ` [PATCH] FC Transport support for vports based on NPIV James Smart
2007-05-21 15:27 ` Christof Schmitt
2007-05-21 15:45 ` James Smart
2007-05-22 10:40 ` Christof Schmitt
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=20070514121239.GA23620@schmichrtp \
--to=christof.schmitt@de.ibm.com \
--cc=James.Smart@Emulex.Com \
--cc=duane.grigsby@qlogic.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 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).