<?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: What nata means for you	</title>
	<atom:link href="https://www.dragonflydigest.com/2006/12/05/what-nata-means-for-you/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2006/12/05/what-nata-means-for-you/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Thu, 07 Dec 2006 19:52:59 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: Joe "Floid" Kanowitz		</title>
		<link>https://www.dragonflydigest.com/2006/12/05/what-nata-means-for-you/comment-page-1/#comment-3638</link>

		<dc:creator><![CDATA[Joe "Floid" Kanowitz]]></dc:creator>
		<pubDate>Thu, 07 Dec 2006 19:52:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/index.php/2006/12/05/2006.html#comment-3638</guid>

					<description><![CDATA[Another question from me out in the peanut gallery...
Has the ATA code grown anything like the &quot;disk-level transaction clustering&quot; patch being experimented with on NetBSD a few years ago?

http://kerneltrap.org/node/410
http://www.blasted-heath.com/nbsd/cluster/

I questioned that at the time (as one of the anonymous cowards in the Kerneltrap thread, no less), but that was before I discovered the areal density of a cheap 120+GB ATA drive with no support for command queuing absolutely stomps any possible benefit from TCQ with older drives on a &#039;plain old&#039; UWSCSI bus.  On a single-user desktop, anyway.  

On top of that, I now I realize I may&#039;ve misunderstood the thing and it may only be clustering transactions that were already contiguous, but I&#039;m not doing a good job of actually reading the code while trying to get out the door for work. :}

[I do have time to notice that Storagereview.com&#039;s &quot;IOMeter File Server - 64 I/O in IO/Sec&quot; test actually shows a difference between TCQ/NCQ and no queueing, though I also can&#039;t tell if the scores are in any particular real-life units.]


Now watch as I quite probably post this twice. :P]]></description>
			<content:encoded><![CDATA[<p>Another question from me out in the peanut gallery&#8230;<br />
Has the ATA code grown anything like the &#8220;disk-level transaction clustering&#8221; patch being experimented with on NetBSD a few years ago?</p>
<p><a href="http://kerneltrap.org/node/410" rel="nofollow ugc">http://kerneltrap.org/node/410</a><br />
<a href="http://www.blasted-heath.com/nbsd/cluster/" rel="nofollow ugc">http://www.blasted-heath.com/nbsd/cluster/</a></p>
<p>I questioned that at the time (as one of the anonymous cowards in the Kerneltrap thread, no less), but that was before I discovered the areal density of a cheap 120+GB ATA drive with no support for command queuing absolutely stomps any possible benefit from TCQ with older drives on a &#8216;plain old&#8217; UWSCSI bus.  On a single-user desktop, anyway.  </p>
<p>On top of that, I now I realize I may&#8217;ve misunderstood the thing and it may only be clustering transactions that were already contiguous, but I&#8217;m not doing a good job of actually reading the code while trying to get out the door for work. :}</p>
<p>[I do have time to notice that Storagereview.com&#8217;s &#8220;IOMeter File Server &#8211; 64 I/O in IO/Sec&#8221; test actually shows a difference between TCQ/NCQ and no queueing, though I also can&#8217;t tell if the scores are in any particular real-life units.]</p>
<p>Now watch as I quite probably post this twice. :P</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joe "Floid" Kanowitz		</title>
		<link>https://www.dragonflydigest.com/2006/12/05/what-nata-means-for-you/comment-page-1/#comment-3637</link>

		<dc:creator><![CDATA[Joe "Floid" Kanowitz]]></dc:creator>
		<pubDate>Thu, 07 Dec 2006 19:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/index.php/2006/12/05/2006.html#comment-3637</guid>

					<description><![CDATA[Another question from me out in the peanut gallery...
Has the ATA code grown anything like the &quot;disk-level transaction clustering&quot; patch being experimented with on NetBSD a few years ago?

http://kerneltrap.org/node/410
http://www.blasted-heath.com/nbsd/cluster/

I questioned that at the time (as one of the anonymous cowards in the Kerneltrap thread, no less), but that was before I discovered the areal density of a cheap 120+GB ATA drive with no support for command queuing absolutely stomps any possible benefit from TCQ with older drives on a &#039;plain old&#039; UWSCSI bus.  On a single-user desktop, anyway.  

On top of that, I now I realize I may&#039;ve misunderstood the thing and it may only be clustering transactions that were already contiguous, but I&#039;m not doing a good job of actually reading the code while trying to get out the door for work. :}

[I do have time to notice that Storagereview.com&#039;s &quot;IOMeter File Server - 64 I/O in IO/Sec&quot; test actually shows a difference between TCQ/NCQ and no queueing, though I also can&#039;t tell if the scores are in any particular real-life units.]]]></description>
			<content:encoded><![CDATA[<p>Another question from me out in the peanut gallery&#8230;<br />
Has the ATA code grown anything like the &#8220;disk-level transaction clustering&#8221; patch being experimented with on NetBSD a few years ago?</p>
<p><a href="http://kerneltrap.org/node/410" rel="nofollow ugc">http://kerneltrap.org/node/410</a><br />
<a href="http://www.blasted-heath.com/nbsd/cluster/" rel="nofollow ugc">http://www.blasted-heath.com/nbsd/cluster/</a></p>
<p>I questioned that at the time (as one of the anonymous cowards in the Kerneltrap thread, no less), but that was before I discovered the areal density of a cheap 120+GB ATA drive with no support for command queuing absolutely stomps any possible benefit from TCQ with older drives on a &#8216;plain old&#8217; UWSCSI bus.  On a single-user desktop, anyway.  </p>
<p>On top of that, I now I realize I may&#8217;ve misunderstood the thing and it may only be clustering transactions that were already contiguous, but I&#8217;m not doing a good job of actually reading the code while trying to get out the door for work. :}</p>
<p>[I do have time to notice that Storagereview.com&#8217;s &#8220;IOMeter File Server &#8211; 64 I/O in IO/Sec&#8221; test actually shows a difference between TCQ/NCQ and no queueing, though I also can&#8217;t tell if the scores are in any particular real-life units.]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
