Tech Road Map: Keep An Eye On Virtual I/O

New offerings and approaches feed multicore servers the virtual bandwidth they need.

Multicore servers allow organizations to consolidate 20 or more production servers into each virtual server host, saving space, power, and staff resources in the process. But feeding these servers enough I/O bandwidth has become a major headache for many data centers.

Some experts recommend Gigabit Ethernet connections for each processor core on the host to ensure sufficient bandwidth, dedicated connections for management and virtual machine migration, plus additional Fibre Channel or Gigabit Ethernet connections for storage, resulting in cable and switch port sprawl.


More Software Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

InformationWeek Reports

Leading vendors, including many Fibre Channel providers, are pushing enhanced 10-Gbps Ethernet with Fibre Channel over Ethernet (FCoE) as the solution. Granted, 10-Gbps Ethernet addresses the bandwidth issue, and FCoE converged network adapters can handle the storage side of the equation. However, the standards for both FCoE and Date Center Bridging, the IEEE name for the Ethernet enhancements FCoE requires, haven't yet been ratified.

DIG DEEPER
Virtualization Showdown
We put leading VM platforms to the test.
Other vendors have proposed solutions to the virtual server I/O problem that could be more cost-effective and flexible. These systems create multiple virtual-aware adapters (virtual network interface cards and virtual host bus adapters) assigned to virtual machines. As the VMs migrate from host to host, the virtual NICs and virtual HBAs let them keep their MAC address or World Wide Name, alleviating some network security and zoning issues of VMs.

Virtualization-aware I/O devices' support for quality of service means that virtual NICs and HBAs supporting critical or latency-sensitive applications can use reserved bandwidth and take higher priority than users surfing Facebook while sharing a single physical connection.


Page 2:  To InfiniBand And Beyond
 1 | 2 |3 |Next Page » 

Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links