<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Linux SFQ experimentation</title>
	<atom:link href="http://www.coverfire.com/archives/2009/06/28/linux-sfq-experimentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coverfire.com/archives/2009/06/28/linux-sfq-experimentation/</link>
	<description>Thoughts and musings</description>
	<lastBuildDate>Sun, 15 Jan 2012 21:25:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan Siemon</title>
		<link>http://www.coverfire.com/archives/2009/06/28/linux-sfq-experimentation/comment-page-1/#comment-378984</link>
		<dc:creator>Dan Siemon</dc:creator>
		<pubDate>Sat, 23 Jul 2011 14:51:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.coverfire.com/?p=622#comment-378984</guid>
		<description>I use an old PC. Kinda power hungry but it makes it a lot easier to test new things.

I&#039;ve been having some PMTU troubles with newer kernels and IPIP tunnels. Once that&#039;s figured out I&#039;ll hopefully do some more experimentation.</description>
		<content:encoded><![CDATA[<p>I use an old PC. Kinda power hungry but it makes it a lot easier to test new things.</p>
<p>I&#8217;ve been having some PMTU troubles with newer kernels and IPIP tunnels. Once that&#8217;s figured out I&#8217;ll hopefully do some more experimentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hechacker1</title>
		<link>http://www.coverfire.com/archives/2009/06/28/linux-sfq-experimentation/comment-page-1/#comment-378942</link>
		<dc:creator>hechacker1</dc:creator>
		<pubDate>Sat, 23 Jul 2011 00:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.coverfire.com/?p=622#comment-378942</guid>
		<description>Hmmm. Yeah, today I spent a lot of time working with the Tomato 2.6.22 kernel base, and it seems back-porting newer kernel schedulers is a waste of time.

I gave pfifo a shot at back-porting, and even that depends on pervasive kernel changes.

DD-WRT and OpenWRT use 2.6.24/25 kernels, but those are that different from the 2.6.22 base I have.


Sooooo, with that in mind, all I can really do is tweak the perturb and limits.

I&#039;ve set perturb to 15 seconds, and limits to 2 for sfq. That generally works out well for 1Mbit or less uplinks.

I would appreciate a test to see if the newer SFQ fixes the spikes.

It may just be the case that these little SOHO routers are just not the best thing to work with for scheduling, since they are often stuck on old kernels. It would take significant work to update their kernels.

The best solution it seems is some type of small linux computer (wall plug server) that can easily be updated with newer versions.</description>
		<content:encoded><![CDATA[<p>Hmmm. Yeah, today I spent a lot of time working with the Tomato 2.6.22 kernel base, and it seems back-porting newer kernel schedulers is a waste of time.</p>
<p>I gave pfifo a shot at back-porting, and even that depends on pervasive kernel changes.</p>
<p>DD-WRT and OpenWRT use 2.6.24/25 kernels, but those are that different from the 2.6.22 base I have.</p>
<p>Sooooo, with that in mind, all I can really do is tweak the perturb and limits.</p>
<p>I&#8217;ve set perturb to 15 seconds, and limits to 2 for sfq. That generally works out well for 1Mbit or less uplinks.</p>
<p>I would appreciate a test to see if the newer SFQ fixes the spikes.</p>
<p>It may just be the case that these little SOHO routers are just not the best thing to work with for scheduling, since they are often stuck on old kernels. It would take significant work to update their kernels.</p>
<p>The best solution it seems is some type of small linux computer (wall plug server) that can easily be updated with newer versions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Siemon</title>
		<link>http://www.coverfire.com/archives/2009/06/28/linux-sfq-experimentation/comment-page-1/#comment-378851</link>
		<dc:creator>Dan Siemon</dc:creator>
		<pubDate>Fri, 22 Jul 2011 00:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.coverfire.com/?p=622#comment-378851</guid>
		<description>I never figured out the source of those spikes for certain but I&#039;m pretty sure it wasn&#039;t due to the size of the queue. There&#039;s been some fixes to SFQ in recent kernels. I should try running these tests again to see if it is fixed.

I doubt there is an optimal perturb time but if the latency spikes I observed have been fixed then there probably isn&#039;t much downside to a short interval.</description>
		<content:encoded><![CDATA[<p>I never figured out the source of those spikes for certain but I&#8217;m pretty sure it wasn&#8217;t due to the size of the queue. There&#8217;s been some fixes to SFQ in recent kernels. I should try running these tests again to see if it is fixed.</p>
<p>I doubt there is an optimal perturb time but if the latency spikes I observed have been fixed then there probably isn&#8217;t much downside to a short interval.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hechacker1</title>
		<link>http://www.coverfire.com/archives/2009/06/28/linux-sfq-experimentation/comment-page-1/#comment-377145</link>
		<dc:creator>hechacker1</dc:creator>
		<pubDate>Sun, 03 Jul 2011 20:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.coverfire.com/?p=622#comment-377145</guid>
		<description>Any thoughts on an optimal perturb time? Or perhaps pfifo with a lower packet limit is the best solution if we want to avoid large spikes in latency?

I&#039;m currently working to compile a custom firmware for WRT54GL routers, using some suggestions you have tested to reduce bufferbloat.

Any input would be helpful.</description>
		<content:encoded><![CDATA[<p>Any thoughts on an optimal perturb time? Or perhaps pfifo with a lower packet limit is the best solution if we want to avoid large spikes in latency?</p>
<p>I&#8217;m currently working to compile a custom firmware for WRT54GL routers, using some suggestions you have tested to reduce bufferbloat.</p>
<p>Any input would be helpful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

