2007
DOI: 10.1147/rd.511.0103
|View full text |Cite
|
Sign up to set email alerts
|

Sharing FCP adapters through virtualization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2008
2008
2012
2012

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 2 publications
0
2
0
Order By: Relevance
“…Overview of T10 data integrity field The FCP channel [6,7] on zEnterprise supports end-to-end data protection, as defined by recent enhancements to the SCSI standard for direct-access block devices, in particular disks, i.e., defined in the International Committee for Information Technology Standards (INCITS) documents [8,9]. This standard introduces an 8-byte data integrity field (DIF) that is appended to each data block, thus increasing the typical 512-byte SCSI block size to 520 bytes.…”
Section: Fcp End-to-end Data Protectionmentioning
confidence: 99%
“…Overview of T10 data integrity field The FCP channel [6,7] on zEnterprise supports end-to-end data protection, as defined by recent enhancements to the SCSI standard for direct-access block devices, in particular disks, i.e., defined in the International Committee for Information Technology Standards (INCITS) documents [8,9]. This standard introduces an 8-byte data integrity field (DIF) that is appended to each data block, thus increasing the typical 512-byte SCSI block size to 520 bytes.…”
Section: Fcp End-to-end Data Protectionmentioning
confidence: 99%
“…This would necessitate purchase of a potentially significant number of HBAs, regardless of whether each VM has a workload that fully utilizes the capacity of an HBA. Typically, servers do not even provide for the installation of a large number of HBAs that would be required to accommodate the number of VMs a server can host, which can be more than a thousand in configurations such as IBM System z9 with z/VM [5] or 32 VMs by using hypervisors like Microsoft Virtual Server 2005 and VMWare ESX on an offthe-shelf server. Hence, a need for a new mechanism to allow the sharing of a physical N_Port among the VMs, providing an addressing capability to uniquely identify each VM to the SAN fabric and allow use of existing SAN zoning techniques to ensure security and eliminate the limitations mentioned above was necessitated.…”
Section: Introductionmentioning
confidence: 99%