View Single Post
  #1 (permalink)  
Old 08-21-2009, 03:18 PM
raidzero's Avatar
raidzero
N00b
Offline
Location: PPCG
 
Join Date: Dec 2008
Posts: 2,193
Reputation: 5220
raidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the communityraidzero is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via MSN to raidzero
WM 6.5 - benefits of modules vs files and you?

I have learned that modules have dedicated spots in RAM where they go when they load, same slot every time. This is the point of G'reloc or WM'reloc. When converting from module to file with recmod, we gain another module slot. In a VK we have an option to limit the maximum number of modules allowed. this is in my kitchen set to 535. I only have around 480 modules left in my ROM. is there anything to be gained from lowering the number of allowed modules? Is there any benefit to having more files than modules or vice versa? I am not so well-versed in windows mobile memory management. It seems to me like having DLLs as files would increase performance because they would not have to be translated, compiled, or whatever (if they even are at load time) and also keep module slots free, but if each module already has its home set in stone does it really matter about the number of free slots? Is this like the old argument of linux kernel modules vs inbuilt drivers? they must each have their pros and cons....

if this makes any sense to anyone I would love to hear opinions, or even better: facts on this matter.


Thanks!
__________________

Last edited by raidzero; 08-21-2009 at 03:21 PM.
Reply With Quote