<?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: Pondering Fibre Channel over Ethernet</title>
	<atom:link href="http://www.aboutrestore.com/2009/09/25/pondering-fibre-channel-over-ethernet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.aboutrestore.com/2009/09/25/pondering-fibre-channel-over-ethernet/</link>
	<description>Blogging about backup, recovery and marketing in the storage industry.</description>
	<lastBuildDate>Mon, 06 Sep 2010 16:25:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jay Livens</title>
		<link>http://www.aboutrestore.com/2009/09/25/pondering-fibre-channel-over-ethernet/comment-page-1/#comment-4783</link>
		<dc:creator>Jay Livens</dc:creator>
		<pubDate>Tue, 29 Sep 2009 14:33:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.aboutrestore.com/?p=809#comment-4783</guid>
		<description>Nigel,

Thank you for your comment; you bring up a great point that iSCSI could benefit from the same advanced networking features required by FCoE.  

I think that the challenge comes back to cost.  If these features can be implemented cost effectively then they will be relevant to iSCSI. If a substantial premium is charged versus vanilla 10 GigE then I thing that most iSCSI users with stick with standard 10 GigE as a &quot;good enough&quot; solution.</description>
		<content:encoded><![CDATA[<p>Nigel,</p>
<p>Thank you for your comment; you bring up a great point that iSCSI could benefit from the same advanced networking features required by FCoE.  </p>
<p>I think that the challenge comes back to cost.  If these features can be implemented cost effectively then they will be relevant to iSCSI. If a substantial premium is charged versus vanilla 10 GigE then I thing that most iSCSI users with stick with standard 10 GigE as a &#8220;good enough&#8221; solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nigel</title>
		<link>http://www.aboutrestore.com/2009/09/25/pondering-fibre-channel-over-ethernet/comment-page-1/#comment-4782</link>
		<dc:creator>Nigel</dc:creator>
		<pubDate>Sun, 27 Sep 2009 18:20:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.aboutrestore.com/?p=809#comment-4782</guid>
		<description>Good concise post and a very balanced view (in my opinion).

An interesting twist to the storey could lie in the fact that iSCSI can also benefit from many of the enhancements in Enhanced Ethernet.  For example, Priority based Flow Control (802.3Qbb) and Enhanced Transmission Selection (802.1Qaz).  

My understanding is that it is possible, for example, to give iSCSI frames, obviously encapsulated in IPv4 frames as normal, a high priority meaning that iSCSI can benefit from lossless behaviour………….. up to a point.  I say “up to a point”, because if iSCSI were to co-exist with FCoE or any other traffic type that required higher priority, it would have to sit lower down the pecking order and be more likely to have PAUSE conditions inflicted.  E.g. If FCoE and iSCSI were operating on the same unified fabric and the fabric started to experience congestion, FCoE would be given a higher priority than iSCSI, BUT iSCSI could still have a higher priority than other traffic types.  Hope Im making sense.

Of course, if iSCSI were also running over Enhanced Ethernet, it would benefit from the better physical aspects too including higher rated cabling and hardware meaning less packets drops for other reasons etc.

Just my penny’s worth.</description>
		<content:encoded><![CDATA[<p>Good concise post and a very balanced view (in my opinion).</p>
<p>An interesting twist to the storey could lie in the fact that iSCSI can also benefit from many of the enhancements in Enhanced Ethernet.  For example, Priority based Flow Control (802.3Qbb) and Enhanced Transmission Selection (802.1Qaz).  </p>
<p>My understanding is that it is possible, for example, to give iSCSI frames, obviously encapsulated in IPv4 frames as normal, a high priority meaning that iSCSI can benefit from lossless behaviour………….. up to a point.  I say “up to a point”, because if iSCSI were to co-exist with FCoE or any other traffic type that required higher priority, it would have to sit lower down the pecking order and be more likely to have PAUSE conditions inflicted.  E.g. If FCoE and iSCSI were operating on the same unified fabric and the fabric started to experience congestion, FCoE would be given a higher priority than iSCSI, BUT iSCSI could still have a higher priority than other traffic types.  Hope Im making sense.</p>
<p>Of course, if iSCSI were also running over Enhanced Ethernet, it would benefit from the better physical aspects too including higher rated cabling and hardware meaning less packets drops for other reasons etc.</p>
<p>Just my penny’s worth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
