|| ||Dave Chinner <david-AT-fromorbit.com>|
|| ||Jared Hulbert <jaredeh-AT-gmail.com>|
|| ||Re: [PATCH 00/10] AXFS: Advanced XIP filesystem|
|| ||Thu, 21 Aug 2008 18:39:16 +1000|
|| ||Linux-kernel-AT-vger.kernel.org, linux-embedded-AT-vger.kernel.org,
=?iso-8859-1?Q?J=F6rn?= Engel <joern-AT-logfs.org>,
tim.bird-AT-AM.SONY.COM, cotte-AT-de.ibm.com, nickpiggin-AT-yahoo.com.au|
On Wed, Aug 20, 2008 at 10:44:36PM -0700, Jared Hulbert wrote:
> I'd like to get a first round of review on my AXFS filesystem. 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.
FWIW, I'm not sure it's a good idea to name this new filesystem AXFS.
People are almost certainly going to confuse it with XFS despite
the filesystems being aimed at diammetrically opposed ends of the
storage spectrum. ;)
to post comments)