<?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: A short npf note	</title>
	<atom:link href="https://www.dragonflydigest.com/2013/03/23/a-short-npf-note/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2013/03/23/a-short-npf-note/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Tue, 26 Mar 2013 03:59:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: corey		</title>
		<link>https://www.dragonflydigest.com/2013/03/23/a-short-npf-note/comment-page-1/#comment-47923</link>

		<dc:creator><![CDATA[corey]]></dc:creator>
		<pubDate>Tue, 26 Mar 2013 03:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11452#comment-47923</guid>

					<description><![CDATA[I think &quot;how pf would be had it been written today&quot; is a bit of a stretch. There are many other aspects of pf besides whether its packet-filtering engine can utilize multiple cores. I don&#039;t believe the OpenBSD pf  devs see lack of multicore packet filtering as a big handicap on that platform.

While running multi-core was a consideration, I suspect the porting effort was one, too, as OpenBSD pf has become more tightly integrated with its kernel.]]></description>
			<content:encoded><![CDATA[<p>I think &#8220;how pf would be had it been written today&#8221; is a bit of a stretch. There are many other aspects of pf besides whether its packet-filtering engine can utilize multiple cores. I don&#8217;t believe the OpenBSD pf  devs see lack of multicore packet filtering as a big handicap on that platform.</p>
<p>While running multi-core was a consideration, I suspect the porting effort was one, too, as OpenBSD pf has become more tightly integrated with its kernel.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: js		</title>
		<link>https://www.dragonflydigest.com/2013/03/23/a-short-npf-note/comment-page-1/#comment-47745</link>

		<dc:creator><![CDATA[js]]></dc:creator>
		<pubDate>Sun, 24 Mar 2013 12:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11452#comment-47745</guid>

					<description><![CDATA[s/how of/how pf/, sorry.]]></description>
			<content:encoded><![CDATA[<p>s/how of/how pf/, sorry.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: js		</title>
		<link>https://www.dragonflydigest.com/2013/03/23/a-short-npf-note/comment-page-1/#comment-47744</link>

		<dc:creator><![CDATA[js]]></dc:creator>
		<pubDate>Sun, 24 Mar 2013 12:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=11452#comment-47744</guid>

					<description><![CDATA[npf is not a fork, but a conplete rewrite with multiprocessing being part of its design from the start. It&#039;s basically how of would be if it would have been written today.]]></description>
			<content:encoded><![CDATA[<p>npf is not a fork, but a conplete rewrite with multiprocessing being part of its design from the start. It&#8217;s basically how of would be if it would have been written today.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
