Manual

Higher Eciency
FlexSuite Adapters feature QLogic I/OFlex technology, a eld-
congurable upgrade to use the same hardware for Gen 5 Fibre
Channel or 10GbE server connecvity.
FlexSuite
In Transacon-Intensive and Bandwidth-Intensive Environments
For virtualized environments, the most crical measure of performance is the ability to scale as the number
of VMs and applicaon workloads increase. In tesng conducted by QLogic, the QLE2672 FlexSuite Gen 5
Fibre Channel Adapter delivered:
 3X the transacons and 2X the bandwidth of 8Gb Fibre Channel Adapters.
 The QLE2672 also demonstrated a 50 percent advantage over compeve products for read-only
performance and 25 percent beer mixed read-write performance.
This superior performance of QLogic Gen 5 Fibre Channel Adapters translates to support for both higher VM
density and more demanding Tier-1 applicaons.
QLogic achieves superior performance by leveraging the advanced Gen 5 Fibre Channel and PCIe Gen3
specicaons—while maintaining backwards compability with exisng Fibre Channel networks. The unique
port-isolaon architecture of the QLogic FlexSuite Adapters ensures data integrity, security, and determinisc
scalable performance to drive storage trac at line rate across all ports.
Furthermore, QoS enables IT administrators to control and priorize trac.
10GbE Intelligent Networking Eliminates I/O Bolenecks
QLogic’s 10GbE intelligent Ethernet architecture, combined with new virtualizaon soware features, allow
mulple and exible receive queues, such as NetQueue, and signicantly reduces the delays inherent in
current virtualizaon implementaons by:
• Eliminang some of the hypervisor overhead. This frees up processor resources to support heavier weight
applicaons on the VMs or to run more VMs per server.
• Eliminang the queuing boleneck in today’s soware-based approach. The current approach creates a
single rst-in, rst-out queue for incoming packets from the Ethernet adapter through the hypervisor to the
various VMs. Because neither the hypervisor nor the Ethernet adapter knows which packet goes to which
interface, there is substanal packet processing performed in the hypervisor to determine which packet goes
where. It is a processor-intensive task that consumes a great deal of me and CPU cycles.