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? No complaint if not, it would be a nice bonus though. -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html