<?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: RDMA on Converged Ethernet</title>
	<atom:link href="http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/</link>
	<description>Linux hacker, recovering mathematician, former athlete</description>
	<lastBuildDate>Fri, 11 Mar 2011 20:17:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: James</title>
		<link>http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/comment-page-1/#comment-1017</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 06 May 2010 11:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://digitalvampire.org/blog/?p=76#comment-1017</guid>
		<description>Apparently you can use SoftRoCE by systemfabricworks to use standard ethernet NICs to try out RoCE without any specific hardware as such. Obviously the performance will not be nearly as good as it would with some of the Mellanox cards or whatever, but it could be a good starting point!</description>
		<content:encoded><![CDATA[<p>Apparently you can use SoftRoCE by systemfabricworks to use standard ethernet NICs to try out RoCE without any specific hardware as such. Obviously the performance will not be nearly as good as it would with some of the Mellanox cards or whatever, but it could be a good starting point!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/comment-page-1/#comment-979</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 05 May 2010 00:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://digitalvampire.org/blog/?p=76#comment-979</guid>
		<description>@roland, I loved your article and pretty much agree with it entirely. I do believe that RoCE will only pick up if you can use fairly standard ethernet NICs, is this the case? Roland, do you know if it&#039;s so? Some datacenters, and some circumstances don&#039;t make TCP the ideal protocol, and although iWARP does make a huge difference, if you want to avoid TCP, RoCE does seem like a fairly decent alternative.... the fact that infiniband uses a credit/token based protocol sometimes does yield it&#039;s benefits with regard to flow control, although it&#039;s true that it&#039;s implementation of reliability may be more complex than TCP altogether. Love your blog Roland!! :-)</description>
		<content:encoded><![CDATA[<p>@roland, I loved your article and pretty much agree with it entirely. I do believe that RoCE will only pick up if you can use fairly standard ethernet NICs, is this the case? Roland, do you know if it&#8217;s so? Some datacenters, and some circumstances don&#8217;t make TCP the ideal protocol, and although iWARP does make a huge difference, if you want to avoid TCP, RoCE does seem like a fairly decent alternative&#8230;. the fact that infiniband uses a credit/token based protocol sometimes does yield it&#8217;s benefits with regard to flow control, although it&#8217;s true that it&#8217;s implementation of reliability may be more complex than TCP altogether. Love your blog Roland!! <img src='http://digitalvampire.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland&#8217;s Blog &#187; Blog Archive &#187; Rocky roads</title>
		<link>http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/comment-page-1/#comment-926</link>
		<dc:creator>Roland&#8217;s Blog &#187; Blog Archive &#187; Rocky roads</dc:creator>
		<pubDate>Mon, 19 Apr 2010 23:16:52 +0000</pubDate>
		<guid isPermaLink="false">http://digitalvampire.org/blog/?p=76#comment-926</guid>
		<description>[...] announced the &#8220;RDMA over Converged Ethernet (RoCE)&#8221; specification today.  I&#8217;ve already discussed my thoughts on the underlying technology (although I have a bit more to say), so for now I just [...]</description>
		<content:encoded><![CDATA[<p>[...] announced the &#8220;RDMA over Converged Ethernet (RoCE)&#8221; specification today.  I&#8217;ve already discussed my thoughts on the underlying technology (although I have a bit more to say), so for now I just [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roland</title>
		<link>http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/comment-page-1/#comment-880</link>
		<dc:creator>roland</dc:creator>
		<pubDate>Mon, 28 Sep 2009 17:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://digitalvampire.org/blog/?p=76#comment-880</guid>
		<description>@Pete: A) not sure why you wouldn&#039;t look at it as IBoE -- taking IB transport protocol and changing the L2 encapsulation to ethernet sure looks like exactly what IBoE means.  You might be able to make a proprietary protocol quickly but are you going to be able to do enough research/simulation to handle congestion stably, etc?  And you have to figure out how to tie into ethernet multicast management (most 10 gig ethernet switches are going to do IGMP snooping), do address discovery to know how to talk to other endpoints, etc.

B) Yes, TCP introduces some overhead on the NIC, but you need some reliability protocol (and if anything, the IB RC protocol is more complex in some ways than TCP, with multiple kinds of ACK/NAKs etc).  And TCP offload is a solved problem at this point anyway -- cf Chelsio, NetEffect/Intel, etc.</description>
		<content:encoded><![CDATA[<p>@Pete: A) not sure why you wouldn&#8217;t look at it as IBoE &#8212; taking IB transport protocol and changing the L2 encapsulation to ethernet sure looks like exactly what IBoE means.  You might be able to make a proprietary protocol quickly but are you going to be able to do enough research/simulation to handle congestion stably, etc?  And you have to figure out how to tie into ethernet multicast management (most 10 gig ethernet switches are going to do IGMP snooping), do address discovery to know how to talk to other endpoints, etc.</p>
<p>B) Yes, TCP introduces some overhead on the NIC, but you need some reliability protocol (and if anything, the IB RC protocol is more complex in some ways than TCP, with multiple kinds of ACK/NAKs etc).  And TCP offload is a solved problem at this point anyway &#8212; cf Chelsio, NetEffect/Intel, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://digitalvampire.org/blog/index.php/2009/03/25/rdma-on-converged-ethernet/comment-page-1/#comment-879</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 25 Sep 2009 22:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://digitalvampire.org/blog/?p=76#comment-879</guid>
		<description>Doing some investigation and I have to agree with Andy.  A) I do not look at it as IBoE.  I think I could make a proprietary
RDMA protocol between two intelligent NICs pretty quick.  And B) the effort and overhead of running the TCP/IP on the Nic I would like to avoid.  This is the research that brought me here.  Looking for a non-proprietary standard non-TCP method.
  These writeups may have motivated me to think more about proprietary, though still researching.</description>
		<content:encoded><![CDATA[<p>Doing some investigation and I have to agree with Andy.  A) I do not look at it as IBoE.  I think I could make a proprietary<br />
RDMA protocol between two intelligent NICs pretty quick.  And B) the effort and overhead of running the TCP/IP on the Nic I would like to avoid.  This is the research that brought me here.  Looking for a non-proprietary standard non-TCP method.<br />
  These writeups may have motivated me to think more about proprietary, though still researching.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

