<?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/"
	xmlns:series="http://unfoldingneurons.com/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: EMC Symmetrix V-Max Is Neither Monolithic Nor Midrange</title>
	<atom:link href="http://gestaltit.com/featured/top/stephen/emc-symmetrix-vmax-neither-nor/feed/" rel="self" type="application/rss+xml" />
	<link>http://gestaltit.com/featured/top/stephen/emc-symmetrix-vmax-neither-nor/</link>
	<description>Independent Experts United</description>
	<lastBuildDate>Wed, 18 Jan 2012 07:24:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Dr. Wolfgang Voigt</title>
		<link>http://gestaltit.com/featured/top/stephen/emc-symmetrix-vmax-neither-nor/comment-page-1/#comment-629</link>
		<dc:creator>Dr. Wolfgang Voigt</dc:creator>
		<pubDate>Sat, 25 Apr 2009 00:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://gestaltit.com/?p=622#comment-629</guid>
		<description>EMC is doing the splits between cost reduction by using commodity hardware and investment protection for the Engenuity firmware. An 3PAR-like solution ( splitting server-mapped volumes in a number of subvolumes behind the controller pairs and I/O delegation via a PCI mesh backplane ) would result in a complete rewriting of the firmware. The V-Max solution has the advantage that the Front-end, Back-end and Cache Director related firmware portions can now run as processes or daemons under the umbrella of an common operating system. This reduces the cost for firmware adoption greatly. Rapid I/O was selected because this protocol contains a lot of storage access control ( locking, messaging, semaphores etc. ). So it becomes possible to build up a unique cache space with the help of special ASICs which translate remote storage accesses in local ones. This is in fact no new idea, it seems only to be a new implementation of ccNUMA ( cache coherent non-uniform memory access ) used by Data General and Sequent in the past. EMC has done a paradigm shift from the Direct Matrix ( based on Ethernet SerDes chips ) to a Dual Fabric Rapid I/O network. In my opinion it would be much better to use the new Infiniband QDR host channel adapter and switch ( 36 ports with 4x 10 Gbps ) ASICs  It is very likely that IBM is going this way to improve the XIV storage system. A big disadvantage of Rapid I/O is the maximal connection distance of 80cm. Therefore Rapid I/O is not the right platform to develop Multi-Site storage solutions based on the ideas of YottaYotta.</description>
		<content:encoded><![CDATA[<p>EMC is doing the splits between cost reduction by using commodity hardware and investment protection for the Engenuity firmware. An 3PAR-like solution ( splitting server-mapped volumes in a number of subvolumes behind the controller pairs and I/O delegation via a PCI mesh backplane ) would result in a complete rewriting of the firmware. The V-Max solution has the advantage that the Front-end, Back-end and Cache Director related firmware portions can now run as processes or daemons under the umbrella of an common operating system. This reduces the cost for firmware adoption greatly. Rapid I/O was selected because this protocol contains a lot of storage access control ( locking, messaging, semaphores etc. ). So it becomes possible to build up a unique cache space with the help of special ASICs which translate remote storage accesses in local ones. This is in fact no new idea, it seems only to be a new implementation of ccNUMA ( cache coherent non-uniform memory access ) used by Data General and Sequent in the past. EMC has done a paradigm shift from the Direct Matrix ( based on Ethernet SerDes chips ) to a Dual Fabric Rapid I/O network. In my opinion it would be much better to use the new Infiniband QDR host channel adapter and switch ( 36 ports with 4x 10 Gbps ) ASICs  It is very likely that IBM is going this way to improve the XIV storage system. A big disadvantage of Rapid I/O is the maximal connection distance of 80cm. Therefore Rapid I/O is not the right platform to develop Multi-Site storage solutions based on the ideas of YottaYotta.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Wolfgang Voigt</title>
		<link>http://gestaltit.com/featured/top/stephen/emc-symmetrix-vmax-neither-nor/comment-page-1/#comment-9</link>
		<dc:creator>Dr. Wolfgang Voigt</dc:creator>
		<pubDate>Fri, 24 Apr 2009 20:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://gestaltit.com/?p=622#comment-9</guid>
		<description>EMC is doing the splits between cost reduction by using commodity hardware and investment protection for the Engenuity firmware. An 3PAR-like solution ( splitting server-mapped volumes in a number of subvolumes behind the controller pairs and I/O delegation via a PCI mesh backplane ) would result in a complete rewriting of the firmware. The V-Max solution has the advantage that the Front-end, Back-end and Cache Director related firmware portions can now run as processes or daemons under the umbrella of an common operating system. This reduces the cost for firmware adoption greatly. Rapid I/O was selected because this protocol contains a lot of storage access control ( locking, messaging, semaphores etc. ). So it becomes possible to build up a unique cache space with the help of special ASICs which translate remote storage accesses in local ones. This is in fact no new idea, it seems only to be a new implementation of ccNUMA ( cache coherent non-uniform memory access ) used by Data General and Sequent in the past. EMC has done a paradigm shift from the Direct Matrix ( based on Ethernet SerDes chips ) to a Dual Fabric Rapid I/O network. In my opinion it would be much better to use the new Infiniband QDR host channel adapter and switch ( 36 ports with 4x 10 Gbps ) ASICs  It is very likely that IBM is going this way to improve the XIV storage system. A big disadvantage of Rapid I/O is the maximal connection distance of 80cm. Therefore Rapid I/O is not the right platform to develop Multi-Site storage solutions based on the ideas of YottaYotta.</description>
		<content:encoded><![CDATA[<p>EMC is doing the splits between cost reduction by using commodity hardware and investment protection for the Engenuity firmware. An 3PAR-like solution ( splitting server-mapped volumes in a number of subvolumes behind the controller pairs and I/O delegation via a PCI mesh backplane ) would result in a complete rewriting of the firmware. The V-Max solution has the advantage that the Front-end, Back-end and Cache Director related firmware portions can now run as processes or daemons under the umbrella of an common operating system. This reduces the cost for firmware adoption greatly. Rapid I/O was selected because this protocol contains a lot of storage access control ( locking, messaging, semaphores etc. ). So it becomes possible to build up a unique cache space with the help of special ASICs which translate remote storage accesses in local ones. This is in fact no new idea, it seems only to be a new implementation of ccNUMA ( cache coherent non-uniform memory access ) used by Data General and Sequent in the past. EMC has done a paradigm shift from the Direct Matrix ( based on Ethernet SerDes chips ) to a Dual Fabric Rapid I/O network. In my opinion it would be much better to use the new Infiniband QDR host channel adapter and switch ( 36 ports with 4x 10 Gbps ) ASICs  It is very likely that IBM is going this way to improve the XIV storage system. A big disadvantage of Rapid I/O is the maximal connection distance of 80cm. Therefore Rapid I/O is not the right platform to develop Multi-Site storage solutions based on the ideas of YottaYotta.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sfoskett</title>
		<link>http://gestaltit.com/featured/top/stephen/emc-symmetrix-vmax-neither-nor/comment-page-1/#comment-8</link>
		<dc:creator>sfoskett</dc:creator>
		<pubDate>Tue, 14 Apr 2009 18:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://gestaltit.com/?p=622#comment-8</guid>
		<description>Indeed, as I said, V-Max is not a virtualization platform. However, it is fair for the company to claim that it is virtualized internally, and impressively so, since there is no link between physical and logical. And yes, I do think that calling it &quot;V-Max&quot; and saying virtual all over the place confuses the audience!</description>
		<content:encoded><![CDATA[<p>Indeed, as I said, V-Max is not a virtualization platform. However, it is fair for the company to claim that it is virtualized internally, and impressively so, since there is no link between physical and logical. And yes, I do think that calling it &#8220;V-Max&#8221; and saying virtual all over the place confuses the audience!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vijay Ramaswamy</title>
		<link>http://gestaltit.com/featured/top/stephen/emc-symmetrix-vmax-neither-nor/comment-page-1/#comment-7</link>
		<dc:creator>Vijay Ramaswamy</dc:creator>
		<pubDate>Tue, 14 Apr 2009 18:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://gestaltit.com/?p=622#comment-7</guid>
		<description>Infact V-Max is not a virtualization platform as the industry knows &#039;storage virtualization&#039; today. It does not provide any of the benefits of heterogeneous external storage virtualization  which it does not appear to do. Customers today have a lot of legacy assets with quite a bit of stranded storage. V-Max cannot help these customers reclaim stranded capacity or improve storage utilization or help with migration issues. V-Max provides a level of abstraction within a box  which surely can be claimed as a type of  &#039;virtualization&#039; after all.  Surely a good strategy on behalf of EMC to  muddle of up and confuse the market.</description>
		<content:encoded><![CDATA[<p>Infact V-Max is not a virtualization platform as the industry knows &#39;storage virtualization&#39; today. It does not provide any of the benefits of heterogeneous external storage virtualization  which it does not appear to do. Customers today have a lot of legacy assets with quite a bit of stranded storage. V-Max cannot help these customers reclaim stranded capacity or improve storage utilization or help with migration issues. V-Max provides a level of abstraction within a box  which surely can be claimed as a type of  &#39;virtualization&#39; after all.  Surely a good strategy on behalf of EMC to  muddle of up and confuse the market.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

