<?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 for An enjoyed kernel apprentice</title>
	<atom:link href="http://blog.coly.li/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.coly.li</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 21 Aug 2010 15:19:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on BeijingLSF 2009 by jebtang</title>
		<link>http://blog.coly.li/?p=24&#038;cpage=1#comment-248</link>
		<dc:creator>jebtang</dc:creator>
		<pubDate>Sat, 21 Aug 2010 15:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=24#comment-248</guid>
		<description>Hi, just wait for the blog for LSF 2010...</description>
		<content:encoded><![CDATA[<p>Hi, just wait for the blog for LSF 2010&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Random I/O &#8212; Is raw device always faster than file system ? by jebtang</title>
		<link>http://blog.coly.li/?p=87&#038;cpage=1#comment-247</link>
		<dc:creator>jebtang</dc:creator>
		<pubDate>Sat, 21 Aug 2010 15:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=87#comment-247</guid>
		<description>This question indeed been asked million time. For testing result, the bufferI/O(page cache) .vs. Driect I/O, the buffer I/O should show better result than direct I/O on the file system level testing. The ext3 in your testing did show this, but ext4 don&#039;t have this behavior. Why? Also, all of testing is read only operation, the page cache almost no use if you didn’t enable the readahead on the block device layer.

I may find a choice to do the compare with read/write mix operation to see the result.
Also, may try to use the iozone to control the I/O block size to see any effect on the result.
Anyways, this is a good approaching to do no-philosophical problem </description>
		<content:encoded><![CDATA[<p>This question indeed been asked million time. For testing result, the bufferI/O(page cache) .vs. Driect I/O, the buffer I/O should show better result than direct I/O on the file system level testing. The ext3 in your testing did show this, but ext4 don&#8217;t have this behavior. Why? Also, all of testing is read only operation, the page cache almost no use if you didn’t enable the readahead on the block device layer.</p>
<p>I may find a choice to do the compare with read/write mix operation to see the result.<br />
Also, may try to use the iozone to control the I/O block size to see any effect on the result.<br />
Anyways, this is a good approaching to do no-philosophical problem </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t waste your SSD blocks by Tamás Kiss</title>
		<link>http://blog.coly.li/?p=124&#038;cpage=1#comment-218</link>
		<dc:creator>Tamás Kiss</dc:creator>
		<pubDate>Tue, 03 Aug 2010 21:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=124#comment-218</guid>
		<description>Hi!

Thank you for the interesting post. I learned much from it.

I noticed though that there is a small error in the post: you mention the &#039;-N&#039; option that specifies the number of inodes for the filesystem, but then in the example at the end you write &#039;-I 16&#039; instead of &#039;-N 16&#039;. Maybe while writing the example you were thinking of another space wasting filesystem feature: the possibility to create large inodes for storing extended attributes. If someone doesn&#039;t use extended attributes, then it is pointless to create the filesystem with large inodes. According to the mkfs.ext3 man page the smallest possible inode size is 128 bytes if you don&#039;t use extended attributes or any other feature that requires the extra inode space.</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Thank you for the interesting post. I learned much from it.</p>
<p>I noticed though that there is a small error in the post: you mention the &#8216;-N&#8217; option that specifies the number of inodes for the filesystem, but then in the example at the end you write &#8216;-I 16&#8242; instead of &#8216;-N 16&#8242;. Maybe while writing the example you were thinking of another space wasting filesystem feature: the possibility to create large inodes for storing extended attributes. If someone doesn&#8217;t use extended attributes, then it is pointless to create the filesystem with large inodes. According to the mkfs.ext3 man page the smallest possible inode size is 128 bytes if you don&#8217;t use extended attributes or any other feature that requires the extra inode space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taobao joins open source by Joris Willems - Amazing Things</title>
		<link>http://blog.coly.li/?p=112&#038;cpage=1#comment-191</link>
		<dc:creator>Joris Willems - Amazing Things</dc:creator>
		<pubDate>Sat, 24 Jul 2010 13:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=112#comment-191</guid>
		<description>Congratulations from Belgium!</description>
		<content:encoded><![CDATA[<p>Congratulations from Belgium!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taobao joins open source by richard</title>
		<link>http://blog.coly.li/?p=112&#038;cpage=1#comment-190</link>
		<dc:creator>richard</dc:creator>
		<pubDate>Sat, 24 Jul 2010 10:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=112#comment-190</guid>
		<description>This is fantastic news - really great news.

For those of us who believe strongly in open software and in China, this is a great day. This sort of move will do more than any campaign I can imagine to promote openness in Chinese development and, at the same time give devs in China a home grown foss product to prove that not only can foss software find a place in China, it can come from here.

Congratulations Taobao... you show &#039;em all!</description>
		<content:encoded><![CDATA[<p>This is fantastic news &#8211; really great news.</p>
<p>For those of us who believe strongly in open software and in China, this is a great day. This sort of move will do more than any campaign I can imagine to promote openness in Chinese development and, at the same time give devs in China a home grown foss product to prove that not only can foss software find a place in China, it can come from here.</p>
<p>Congratulations Taobao&#8230; you show &#8216;em all!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taobao joins open source by Pockey</title>
		<link>http://blog.coly.li/?p=112&#038;cpage=1#comment-177</link>
		<dc:creator>Pockey</dc:creator>
		<pubDate>Tue, 13 Jul 2010 11:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=112#comment-177</guid>
		<description>Congratulations! It&#039;s definitely a good news for all of us :)</description>
		<content:encoded><![CDATA[<p>Congratulations! It&#8217;s definitely a good news for all of us <img src='http://blog.coly.li/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taobao joins open source by Suresh Jayaraman</title>
		<link>http://blog.coly.li/?p=112&#038;cpage=1#comment-167</link>
		<dc:creator>Suresh Jayaraman</dc:creator>
		<pubDate>Thu, 01 Jul 2010 05:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=112#comment-167</guid>
		<description>It seems your efforts have impacted positively and started paying off (though a little first step, it matters a lot sometimes). Way to Go!!</description>
		<content:encoded><![CDATA[<p>It seems your efforts have impacted positively and started paying off (though a little first step, it matters a lot sometimes). Way to Go!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taobao joins open source by colyli</title>
		<link>http://blog.coly.li/?p=112&#038;cpage=1#comment-166</link>
		<dc:creator>colyli</dc:creator>
		<pubDate>Thu, 01 Jul 2010 04:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=112#comment-166</guid>
		<description>Nikanth, thanks for the comments :-)
This is a great team work, many people contribute valuable efforts to make it come to true. Let&#039;s see whether there are more positive news/contributions coming.</description>
		<content:encoded><![CDATA[<p>Nikanth, thanks for the comments <img src='http://blog.coly.li/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
This is a great team work, many people contribute valuable efforts to make it come to true. Let&#8217;s see whether there are more positive news/contributions coming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Taobao joins open source by Nikanth</title>
		<link>http://blog.coly.li/?p=112&#038;cpage=1#comment-165</link>
		<dc:creator>Nikanth</dc:creator>
		<pubDate>Thu, 01 Jul 2010 04:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=112#comment-165</guid>
		<description>Wow! You rock.</description>
		<content:encoded><![CDATA[<p>Wow! You rock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on a conversation on DLM lock levels used in OCFS2 by TaoMa</title>
		<link>http://blog.coly.li/?p=81&#038;cpage=1#comment-159</link>
		<dc:creator>TaoMa</dc:creator>
		<pubDate>Thu, 17 Jun 2010 04:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.coly.li/?p=81#comment-159</guid>
		<description>hi coly, I think it is really not easy for a starter to understand the whole stuff of dlmglue. So thanks for the sharing. ;)</description>
		<content:encoded><![CDATA[<p>hi coly, I think it is really not easy for a starter to understand the whole stuff of dlmglue. So thanks for the sharing. <img src='http://blog.coly.li/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
