<?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:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Bizarre HFS+ Tricks in Mac OS X 10.6 Snow Leopard</title>
	<atom:link href="http://blog.fosketts.net/2009/09/11/bizarre-hfs-tricks-in-mac-os-x-10-6-snow-leopard/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fosketts.net/2009/09/11/bizarre-hfs-tricks-in-mac-os-x-10-6-snow-leopard/</link>
	<description>Understanding the accumulation of data</description>
	<lastBuildDate>Fri, 19 Mar 2010 00:14:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: DGentry</title>
		<link>http://blog.fosketts.net/2009/09/11/bizarre-hfs-tricks-in-mac-os-x-10-6-snow-leopard/comment-page-1/#comment-13964</link>
		<dc:creator>DGentry</dc:creator>
		<pubDate>Tue, 13 Oct 2009 16:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2302#comment-13964</guid>
		<description>Several years ago while working on an embedded system which used CompactFlash, we experimented with an uncompressed ext2 filesystem versus a compressed JFFS2. JFFS2 used dramatically more CPU time, an issue on a 300 MHz MIPS processor, but its overall I/O performance was slightly better because it read so much less data from the CF card.&lt;br&gt;&lt;br&gt;If the ratio of CPU power to disk speed is even wider, as in a typical x86 desktop with one disk, compression should become a more significant performance win.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Several years ago while working on an embedded system which used CompactFlash, we experimented with an uncompressed ext2 filesystem versus a compressed JFFS2. JFFS2 used dramatically more CPU time, an issue on a 300 MHz MIPS processor, but its overall I/O performance was slightly better because it read so much less data from the CF card.</p>
<p>If the ratio of CPU power to disk speed is even wider, as in a typical x86 desktop with one disk, compression should become a more significant performance win.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DGentry</title>
		<link>http://blog.fosketts.net/2009/09/11/bizarre-hfs-tricks-in-mac-os-x-10-6-snow-leopard/comment-page-1/#comment-13759</link>
		<dc:creator>DGentry</dc:creator>
		<pubDate>Tue, 13 Oct 2009 12:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fosketts.net/?p=2302#comment-13759</guid>
		<description>Several years ago while working on an embedded system which used CompactFlash, we experimented with an uncompressed ext2 filesystem versus a compressed JFFS2. JFFS2 used dramatically more CPU time, an issue on a 300 MHz MIPS processor, but its overall I/O performance was slightly better because it read so much less data from the CF card.&lt;br&gt;&lt;br&gt;If the ratio of CPU power to disk speed is even wider, as in a typical x86 desktop with one disk, compression should become a more significant performance win.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start -->Several years ago while working on an embedded system which used CompactFlash, we experimented with an uncompressed ext2 filesystem versus a compressed JFFS2. JFFS2 used dramatically more CPU time, an issue on a 300 MHz MIPS processor, but its overall I/O performance was slightly better because it read so much less data from the CF card.</p>
<p>If the ratio of CPU power to disk speed is even wider, as in a typical x86 desktop with one disk, compression should become a more significant performance win.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>
