Re: [PATCH] fc transport: new attributes for NPIV

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09.01.2006 19:05 Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> On Thu, Jan 05, 2006 at 12:28:45PM -0500, James Smart wrote:
> > 
> > >Problem is that on the mainframe I don't have access to the primary
> > >port. Virtualization is done in adapter microcode. I just have
> > >access to the virtual port.
> > 
> > I was afraid you'd say this... that was the other caveat.
> > 
> > OK - given that the primary port doesn't exist what you have makes
> > a lot of sense. I guess we have the 2 options:
> > - add the 2 attributes per host
> > - create a host and set the attributes  (and this is major overkill)
> > 
[...snip...]
> 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
> aswell, much better than un-understandable three-latter acronyms :)

Another general point of interest is fc_host_statistics for virtual
and physical ports.

There are some stats (most or all non fc4 stats) that only make sense
for the physical port. And there are the fc4 stats that might be
determined for the virtual port.

Having the (overkill) solution of a host for the physical port would
help to sort things out. You could provide
- complete fc_host_statistics for the physical port,
- separate fc4 statistics for each virtual port.

Without a host for the physical port you have the choice between:

(a) providing same fc_host_statistics (of the physical port) for all
virtual ports with the same permanent port name

(b) providing a combination of non fc4 stats of physical port and fc4
stats of virtual port in fc_host_statistics for a virtual port

zfcp currently does (a) with one of the patches sent last week.

Implementing (a) the per virtual port fc4 statistics are missing.
Implementing (b) the overall fc4 statistics are missing which might
help to determine the utilization of the physical link.

But I don't think this justifies the introduction of a dummy-host for
the physical port in case the physical port is not represented by a
normal host.


Regards,

Andreas

-
: 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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux