Hi, > There were very few tests done with later kernel versions, and in all > practical system configurations we tested we found that XIP did not > give real benefits. Usually execution from flash was slower than when > running from RAM, and even booting a (inevitably uncompressed) kernel > from flash is typically slower than loading a compressed image to RUM > and booting from there.
at some point we were testing some hybrid approaches for XIP and that gave some nice results. First of all, the kernel should not necessarily be uncompressed. Because .data and friend sections are copied to RAM anyway, you can compress them. Besides, we had the "weird" XIP kernel version with only run-once code run as XIP (like .initdata), copying the rest of kernel to RAM in the background while initializing things, and it was really fast and didn't produce performance penalty on the further execution. > So except for some highly specialized applications (you may also call > these "exotic" configurations) XIP for the Linux kernel does not make > much sense to me. Well, I'd put it this way: plain XIP usage is obsolete in the most cases, but the idea is still viable if you apply it right :) Thanks, Vitaly _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev