http://kerneltrap.org/taxonomy/term/1132/0 en-local http://kerneltrap.org/AXFS_Advanced_Execute_In_Place_Filesystem <div class="taxonomy-images"><a href="/news/linux" class="taxonomy-image-links"><img src="http://kerneltrap.org/files/category_pictures/K-Linux.gif" alt="Linux news" title="Linux news" width="75" height="75" /></a></div><!-- google_ad_section_start --><p>"<i>I'd like to get a first round of review on my AXFS filesystem,</i>" <a href="http://kerneltrap.org/mailarchive/linux-kernel/2008/8/21/3019604/thread">began Jared Hulbert</a>, describing his new <em>Advanced XIP File System</em> for Linux. XIP stands for eXecute-In-Place. The new filesystem received quite a bit of positive feedback. Jared offered the following description:</p> <blockquote><p>"This is a simple read only compressed filesystem like Squashfs and cramfs. AXFS is special because it also allows for execute-in-place of your applications. It is a major improvement over the cramfs XIP patches that have been floating around for ages. The biggest improvement is in the way AXFS allows for each page to be XIP or not. First, a user collects information about which pages are accessed on a compressed image for each mmap()ed region from /proc/axfs/volume0. That 'profile' is used as an input to the image builder. The resulting image has only the relevant pages uncompressed and XIP. The result is smaller memory sizes and faster launches."</p></blockquote> <!-- google_ad_section_end --><p><a href="http://kerneltrap.org/AXFS_Advanced_Execute_In_Place_Filesystem" target="_blank">read more</a></p> http://kerneltrap.org/AXFS_Advanced_Execute_In_Place_Filesystem#comments AXFS