<?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>Getting system topology information on Windows</title><link>http://blogs.technet.com/b/winserverperformance/archive/2008/09/13/getting-system-topology-information-on-windows.aspx</link><description>On Windows Server 2008 and later, applications can programmatically get information about how the underlying hardware components relate to one another. Examples include spatial locality and memory latency. This article describes how developers can get</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Getting system topology information on Windows</title><link>http://blogs.technet.com/b/winserverperformance/archive/2008/09/13/getting-system-topology-information-on-windows.aspx#3163577</link><pubDate>Thu, 04 Dec 2008 01:42:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3163577</guid><dc:creator>Vince Bridgers</dc:creator><description>&lt;P&gt;Is there a way to know what processor a sockets application thread might assign affinity to in order to get best performance taking advantage of receive side scaling? If the ethernet receive completions are being processed and indicated to the protocol stack on targeted processors, it might make sense for the application to assign affinity to the same processor a connection's ethernet receive completions are being processed on.&lt;/P&gt;
&lt;P&gt;---&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is not supported on Windows7 and before, but it is being considered&amp;nbsp;for future Windows releases.&lt;/P&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3163577" width="1" height="1"&gt;</description></item><item><title>Getting system topology information on Windows; build scalable multi-processor and NUMA</title><link>http://blogs.technet.com/b/winserverperformance/archive/2008/09/13/getting-system-topology-information-on-windows.aspx#3123304</link><pubDate>Sat, 13 Sep 2008 11:00:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3123304</guid><dc:creator>Getting system topology information on Windows; build scalable multi-processor and NUMA</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.ditii.com/2008/09/13/getting-system-topology-information-on-windows-build-scalable-multi-processor-and-numa/"&gt;http://www.ditii.com/2008/09/13/getting-system-topology-information-on-windows-build-scalable-multi-processor-and-numa/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3123304" width="1" height="1"&gt;</description></item></channel></rss>