Re: [PATCH 00/10] AXFS: Advanced XIP filesystem

[Greg Ungerer]

Jamie Lokier wrote:
> Jared Hulbert wrote:
> > 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.
>
> Sounds great, really nice idea.
>
> How does it fare with no MMU?  Can the profiler and image builder lay
> out the XIP pages in such a way that no-MMU mmaps can map those regions?

The key for XIP on noMMU would be the ability to store a
file as one complete contiguous chunk. Can AXFS do this?

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@xxxxxxxxxxxx
Secure Computing Corporation                PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/