Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Software - Microsoft Windows Server 2012 (419.13 kb)
Software - Microsoft Windows Server 2012 (1.12 mb)
Software - Microsoft Windows Server 2012 (1008.04 kb)
Facilidade de uso
Technical white paper | Microsoft Windows Server 2012 SR-IOV
Introduction
Microsoft® Windows® Server 2012 supports Single Root I/O Virtualization (SR-IOV) as a new feature for Hyper-V. SR-IOV is
included in a Peripheral Component Interconnect Special Interest Group (PCI-SIG) specification for partitioning PCI Express
(PCIe) adapter bandwidth. Windows Server 2012 supports SR-IOV through SR-IOV capable PCIe network adapters (NICs).
Partitioning port bandwidth provides several benefits, including:
• Increased I/O data throughput
• Reduced CPU utilization for processing network traffic
• Reduced network path latency
• Support for live migration
For more information on the SR-IOV standard and industry support for the standard, go to the PCI-SIG site at: pcisig.com.
This paper focuses on implementing SR-IOV within Windows Server 2012. The paper includes the requirements and
recommendations for using the Windows Server 2012 SR-IOV feature on HP ProLiant Servers and HP ProLiant server
blades.
Before implementing SR-IOV, first make sure that your server meets the Windows Server 2012 configuration requirements
as established by Microsoft. For details on these requirements, see the Microsoft website at
microsoft.com/library/jj134246.aspx.
For detailed information or to download Windows Server 2012, see the Microsoft Windows Server 2012 home page at
microsoft.com/en-us/server-cloud/windows-server/default.aspx.
Overview of SR-IOV
SR-IOV allows multiple VMs to share a single SR-IOV-capable PCIe NIC while retaining the performance benefit of one PCIe
device to one VM association.
The SR-IOV standard builds on the following PCI standards to extend the PCI configuration space and define access to
Virtual Functions:
• PCIe
• Alternative Routing ID (ARI)
• Address Translation Services (ATS)
• Function Level Reset (FLR)
By assigning a Virtual Function (VF) to each VM, multiple VMs can share a single SR-IOV capable PCIe NIC that may have just
one physical network port.
A Virtual Function is a function that has an association with a Physical Function. Each partition of the PCIe NIC appears in the
PCI configuration space as a Virtual Function with its own configuration space and Base Address Registers (BAR). It shares
the bandwidth of the PCIe NIC with other Physical Functions or Virtual Functions. Characteristics of a Virtual Function include:
• Support for native I/O virtualization
• A PCIe configuration space that defines a unique set of Message Signaled Interrupts (MSI) and MSI-eXtended (MSI-X)
vectors
• A Physical Function is a PCIe function that supports the SR-IOV capabilities. It is a standard PCIe device with its own full PCI
configuration space and set of resources to manage Virtual Functions. Characteristics of a Physical Function include:
• SR-IOV Extended Capability as part of its configuration space
• Configuration information for the Virtual Functions to which it is associated
• Base Address Registers (BAR) configuration and Virtual Function type for any Virtual Functions associated with it
SR-IOV implements bandwidth partitioning by allocating multiple Virtual Functions to a Physical Function. The Virtual
Functions appear as PCI devices that are part of the physical PCI device by their resources (queues and register sets). Instead
of using the Virtual Machine Manager for VM processing, SR-IOV bypasses the VMbus with dedicated hardware queues and a
round-robin scheduler to reduce processor overhead.
Because SR-IOV enumerates Virtual Functions in a hardware-based PCI configuration space, it is well suited for providing
hardware support for virtualization of fixed-function devices. A Virtual Function and Physical Function that are associated
2
...