<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic TCP Off Load Engine (TOE) question in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/tcp-off-load-engine-toe-question/m-p/5480973#M28581</link>
    <description>&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Marc had some NIC/Adapter questions regarding CPU Off Loading capabilities:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*******************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m looking for a NIC adapter with &amp;nbsp;ToE support (TCP Of Load Engine)&lt;/P&gt;&lt;P&gt;Future NC366i is based on Intel i350 ( &lt;A target="_blank" href="http://www.intel.com/Assets/PDF/prodbrief/I350_Family_Product_Brief_v001.pdf"&gt;http://www.intel.com/Assets/PDF/prodbrief/I350_Family_Product_Brief_v001.pdf&lt;/A&gt; ), it supports “LAN accelerations include TCP stateless offloads such as TCP/IP checksum, TCP segmentation, Receive Side Coalescing (RSC), and Receive Side Scaling (RSS) “&lt;/P&gt;&lt;P&gt;Is it the same features than ToE ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Armand replied:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It sounds very similar to actual TCP off-load engine we implement on most of our NIC’s option and for a while.&lt;/P&gt;&lt;P&gt;RSS is supported my Microsoft OS for many years.&lt;/P&gt;&lt;P&gt;RSC seems to be a more recent technology proposed by Intel.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Also from Vincent:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Strictly speaking, TCP Offload Engine refers to running the entire TCP/IP stack on the NIC instead of the host’s CPU. The various offloads you mention are a subset of TCP processing. In particular, “stateless” offloads refer to parts of the protocol that can be processed without maintaining a table of connections with their current state. So I wouldn’t say that TCP stateless offloads is equivalent to TCP Offload Engine, but, depending on context, it might be good enough.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Other comments or input?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jan 2012 22:19:44 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2012-01-11T22:19:44Z</dc:date>
    <item>
      <title>TCP Off Load Engine (TOE) question</title>
      <link>https://community.hpe.com/t5/bladesystem-general/tcp-off-load-engine-toe-question/m-p/5480973#M28581</link>
      <description>&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Marc had some NIC/Adapter questions regarding CPU Off Loading capabilities:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*******************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m looking for a NIC adapter with &amp;nbsp;ToE support (TCP Of Load Engine)&lt;/P&gt;&lt;P&gt;Future NC366i is based on Intel i350 ( &lt;A target="_blank" href="http://www.intel.com/Assets/PDF/prodbrief/I350_Family_Product_Brief_v001.pdf"&gt;http://www.intel.com/Assets/PDF/prodbrief/I350_Family_Product_Brief_v001.pdf&lt;/A&gt; ), it supports “LAN accelerations include TCP stateless offloads such as TCP/IP checksum, TCP segmentation, Receive Side Coalescing (RSC), and Receive Side Scaling (RSS) “&lt;/P&gt;&lt;P&gt;Is it the same features than ToE ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Armand replied:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It sounds very similar to actual TCP off-load engine we implement on most of our NIC’s option and for a while.&lt;/P&gt;&lt;P&gt;RSS is supported my Microsoft OS for many years.&lt;/P&gt;&lt;P&gt;RSC seems to be a more recent technology proposed by Intel.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Also from Vincent:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Strictly speaking, TCP Offload Engine refers to running the entire TCP/IP stack on the NIC instead of the host’s CPU. The various offloads you mention are a subset of TCP processing. In particular, “stateless” offloads refer to parts of the protocol that can be processed without maintaining a table of connections with their current state. So I wouldn’t say that TCP stateless offloads is equivalent to TCP Offload Engine, but, depending on context, it might be good enough.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Other comments or input?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2012 22:19:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/tcp-off-load-engine-toe-question/m-p/5480973#M28581</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2012-01-11T22:19:44Z</dc:date>
    </item>
  </channel>
</rss>

