<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Next Up: I/O Virtualization?</title>
	<atom:link href="http://gigaom.com/2008/02/28/next-up-io-virtualization/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/</link>
	<description>Tracking the Internet Evolution</description>
	<pubDate>Sun, 12 Oct 2008 23:46:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kennyo</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-863758</link>
		<dc:creator>Kennyo</dc:creator>
		<pubDate>Sat, 01 Mar 2008 17:52:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-863758</guid>
		<description>&lt;p&gt;The very cool part of I/O virtualization isn't the fact that it interoperates with all of the other (redundant?) transfer mechanisms, or that it makes it "easy to connect the VM" to different resources... although that's part of it.&lt;/p&gt;

&lt;p&gt;The thing that's valueable is that when one provisions a piece of software to a piece of hardware (whether-or-not it's been virtualized) one can provision a "virtual NIC" at the same time.&lt;/p&gt;

&lt;p&gt;So picture the future: software, I/O, and presumably storage, can be allocated on-the-fly as compute demands dictate. Very much of an automated "cloud" scenario.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The very cool part of I/O virtualization isn&#8217;t the fact that it interoperates with all of the other (redundant?) transfer mechanisms, or that it makes it &#8220;easy to connect the VM&#8221; to different resources&#8230; although that&#8217;s part of it.</p>
<p>The thing that&#8217;s valueable is that when one provisions a piece of software to a piece of hardware (whether-or-not it&#8217;s been virtualized) one can provision a &#8220;virtual NIC&#8221; at the same time.</p>
<p>So picture the future: software, I/O, and presumably storage, can be allocated on-the-fly as compute demands dictate. Very much of an automated &#8220;cloud&#8221; scenario.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-863731</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Sat, 01 Mar 2008 06:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-863731</guid>
		<description>&lt;p&gt;The summary in 2nd paragraph is confusing, and makes it sounds as if this is something like a SAN technology - as far as I can tell from the links, this is simply a way for multiple PCI Express cards in a single system to be allocated to separate virtual machines.  The I/O virtualization part presumably makes it easy to connect a VM to different I/O resources, although SANs already do that so it's hard to see the value of this.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The summary in 2nd paragraph is confusing, and makes it sounds as if this is something like a SAN technology - as far as I can tell from the links, this is simply a way for multiple PCI Express cards in a single system to be allocated to separate virtual machines.  The I/O virtualization part presumably makes it easy to connect a VM to different I/O resources, although SANs already do that so it&#8217;s hard to see the value of this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GaryO</title>
		<link>http://gigaom.com/2008/02/28/next-up-io-virtualization/#comment-863581</link>
		<dc:creator>GaryO</dc:creator>
		<pubDate>Fri, 29 Feb 2008 06:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=11654#comment-863581</guid>
		<description>&lt;p&gt;Great to see GigaOm covering more data center infrastructure!&lt;/p&gt;

&lt;p&gt;In addition to the folks mentioned delivering sophisticated path management, there are also companies trying to minimize the impact of application I/O requests by applying memory at the server, network, and storage layers, and delivering a "virtual I/O" response.&lt;/p&gt;

&lt;p&gt;But more importantly, how the heck did we go from:
1. We have Ethernet to
2. We have Ethernet and Fibre Channel to
3. We have Ethernet, Fibre Channel and InifiniBand to
4. We can put everything back on 10Gig Ethernet.&lt;/p&gt;

&lt;p&gt;Is it just me, or does this seem like we could have saved a few billion dollars over the last few years and skipped a couple of steps?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great to see GigaOm covering more data center infrastructure!</p>
<p>In addition to the folks mentioned delivering sophisticated path management, there are also companies trying to minimize the impact of application I/O requests by applying memory at the server, network, and storage layers, and delivering a &#8220;virtual I/O&#8221; response.</p>
<p>But more importantly, how the heck did we go from:<br />
1. We have Ethernet to<br />
2. We have Ethernet and Fibre Channel to<br />
3. We have Ethernet, Fibre Channel and InifiniBand to<br />
4. We can put everything back on 10Gig Ethernet.</p>
<p>Is it just me, or does this seem like we could have saved a few billion dollars over the last few years and skipped a couple of steps?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
