<?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: OISF engine prototype: threading</title>
	<atom:link href="http://www.inliniac.net/blog/2009/02/28/oisf-engine-prototype-threading.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.inliniac.net/blog/2009/02/28/oisf-engine-prototype-threading.html</link>
	<description>Everything inline.</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:49:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Victor Julien</title>
		<link>http://www.inliniac.net/blog/2009/02/28/oisf-engine-prototype-threading.html/comment-page-1#comment-13080</link>
		<dc:creator>Victor Julien</dc:creator>
		<pubDate>Tue, 10 Mar 2009 17:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=236#comment-13080</guid>
		<description>@Vivek Rajan: Using the option to set CPU (or core) affinity to the threads is possible to make sure all threads processing a single packet remain on the same CPU/core.</description>
		<content:encoded><![CDATA[<p>@Vivek Rajan: Using the option to set CPU (or core) affinity to the threads is possible to make sure all threads processing a single packet remain on the same CPU/core.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vivek Rajan</title>
		<link>http://www.inliniac.net/blog/2009/02/28/oisf-engine-prototype-threading.html/comment-page-1#comment-13077</link>
		<dc:creator>Vivek Rajan</dc:creator>
		<pubDate>Tue, 10 Mar 2009 12:25:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.inliniac.net/blog/?p=236#comment-13077</guid>
		<description>IMHO, this is the wrong way to approach packet processing on multicore. Passing half cooked packets from one thread to another will have cache impact which may severely degrade performance. You must strive to keep the cache of a given core warm, the best way is to use a task stealing approach (do your own or use Cilk or Intel TBB).</description>
		<content:encoded><![CDATA[<p>IMHO, this is the wrong way to approach packet processing on multicore. Passing half cooked packets from one thread to another will have cache impact which may severely degrade performance. You must strive to keep the cache of a given core warm, the best way is to use a task stealing approach (do your own or use Cilk or Intel TBB).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

