Quote:
Originally Posted by joojoobee666
I did just manage to come across this little tidbit:
"The advantage of XIP modules comes into play when one considers the limited amount of RAM available on a typical Windows Mobile device. XIP modules are pre-relocated to a guaranteed available base address, and do not require any runtime alterations to their backing memory when mapped. As a result, XIP modules can be backed entirely by ROM and not RAM, decreasing the (scarce) RAM that must be devoted to holding executable code"
So, if I am reading this correctly, it would be advantageous to convert ANY program/dll that needs to stay loaded/in use for the entire boot into a module. This should in essence free more RAM? (HTC Task Manager is one example, Arcsoft being another, and possibly even some phone/canvas related resources)
|
You are reading incorrectly.
First, unlike regular loading, xip modules have larger boundaries. Loading a code section that barely fills a region is very wasteful.
2nd, "Freeing more ram" is a misleading synopsis. What you are doing is consuming less RAM than you would if multiple programs needed the code section. You are consuming more memory than if no program needed the module.
3rd, scarce resources can be an issue when consumed by never-unloaded xip modules.
The moral: don't convert everything to xip. Candidates for conversion are things which are a) used frequently b) used by multiple programs and c) have code sections just under the boundary size.