<?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: Tuning CFQ &#8211; What Station is That?</title>
	<atom:link href="http://www.linux-mag.com/id/7572/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/7572/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Sat, 05 Oct 2013 13:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: sgtaaron</title>
		<link>http://www.linux-mag.com/id/7572/#comment-7152</link>
		<dc:creator>sgtaaron</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7572/#comment-7152</guid>
		<description>&lt;p&gt;The grammar in this story is terrible.  I read the previous article just now and note that the grammar in that story is bad, too.  Does anybody at Linux Magazine bother to proofread their stories?
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The grammar in this story is terrible.  I read the previous article just now and note that the grammar in that story is bad, too.  Does anybody at Linux Magazine bother to proofread their stories?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: porridge</title>
		<link>http://www.linux-mag.com/id/7572/#comment-7153</link>
		<dc:creator>porridge</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7572/#comment-7153</guid>
		<description>&lt;p&gt;Wow, what a useless article.. should have finished after listing the knobs, if tweaking them didn\&#039;t bring any improvements.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Wow, what a useless article.. should have finished after listing the knobs, if tweaking them didn\&#8217;t bring any improvements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laytonjb</title>
		<link>http://www.linux-mag.com/id/7572/#comment-7154</link>
		<dc:creator>laytonjb</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7572/#comment-7154</guid>
		<description>&lt;p&gt;@porridge,&lt;/p&gt;
&lt;p&gt;Sorry - but a \&quot;no\&quot; answer can be as good as a \&quot;yes\&quot; answer. At least I showed for the test configuration I used and the tests I ran that I saw little improvement. Guess what - at least I now know. I doubt you could have answered that question before the testing.&lt;/p&gt;
&lt;p&gt;Plus, I hope you understand that you can make tweaks but you don\&#039;t know if they help or not, until you actually test them. Plus you should test them with applications that have some meaning to you and you situation. &lt;/p&gt;
&lt;p&gt;If I had found a \&quot;magic\&quot; tweak combination would that have meant anything to you? Maybe or maybe not. Is your hardware the same? Did you run the same tests? Are the tests meaningful to you? Sometimes coming up with a magic tweak doesn\&#039;t help all situations.&lt;/p&gt;
&lt;p&gt;I\&#039;m hoping that people reading the article will learn from it. Obviously you didn\&#039;t. Remember the Thomas Edison phrase, \&quot;If I find 10,000 ways something won\&#039;t work, I haven\&#039;t failed. I am not discouraged, because every wrong attempt discarded is another step forward\&quot;&lt;/p&gt;
&lt;p&gt;Jeff
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@porridge,</p>
<p>Sorry &#8211; but a \&#8221;no\&#8221; answer can be as good as a \&#8221;yes\&#8221; answer. At least I showed for the test configuration I used and the tests I ran that I saw little improvement. Guess what &#8211; at least I now know. I doubt you could have answered that question before the testing.</p>
<p>Plus, I hope you understand that you can make tweaks but you don\&#8217;t know if they help or not, until you actually test them. Plus you should test them with applications that have some meaning to you and you situation. </p>
<p>If I had found a \&#8221;magic\&#8221; tweak combination would that have meant anything to you? Maybe or maybe not. Is your hardware the same? Did you run the same tests? Are the tests meaningful to you? Sometimes coming up with a magic tweak doesn\&#8217;t help all situations.</p>
<p>I\&#8217;m hoping that people reading the article will learn from it. Obviously you didn\&#8217;t. Remember the Thomas Edison phrase, \&#8221;If I find 10,000 ways something won\&#8217;t work, I haven\&#8217;t failed. I am not discouraged, because every wrong attempt discarded is another step forward\&#8221;</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nouiz</title>
		<link>http://www.linux-mag.com/id/7572/#comment-7155</link>
		<dc:creator>nouiz</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7572/#comment-7155</guid>
		<description>&lt;p&gt;Do someone know something similar to the nice program for the cpu, but for the disk?&lt;/p&gt;
&lt;p&gt;It happen from times to times that I must do some very heavy io operation on a nfs server(like du -ch --max-depth 1 ...). I do it locally, but this slow down all user of this nfs server. I don\&#039;t see any way to do this in all the IOScheduler that you presented or in how we can tune them.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;Frédéric Bastien
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Do someone know something similar to the nice program for the cpu, but for the disk?</p>
<p>It happen from times to times that I must do some very heavy io operation on a nfs server(like du -ch &#8211;max-depth 1 &#8230;). I do it locally, but this slow down all user of this nfs server. I don\&#8217;t see any way to do this in all the IOScheduler that you presented or in how we can tune them.</p>
<p>Thanks</p>
<p>Frédéric Bastien</p>
]]></content:encoded>
	</item>
</channel>
</rss>