<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Netmon vs Chimney</title><link>http://blogs.technet.com/tristank/archive/2007/07/23/netmon-vs-chimney.aspx</link><description>I recently encountered TCP Chimney for the first time in the wild. Short version: Chimney is an offload technology that allows the NIC to deal with up to X TCP connections, with any overflow being handled by Windows. All good: get the NIC dealing with</description><dc:language>en-AU</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Post-SP2 TCP Offload Fix</title><link>http://blogs.technet.com/tristank/archive/2007/07/23/netmon-vs-chimney.aspx#3007932</link><pubDate>Mon, 17 Mar 2008 06:31:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3007932</guid><dc:creator>Blog du Tristank</dc:creator><description>&lt;p&gt;I've mentioned Chimney before . Now, a new Windows Update fix for TCP Offload, which turns it off . It&lt;/p&gt;
</description></item></channel></rss>