On Sunday 19 Jan 2003 2:00 pm, Emile van Bergen wrote: > If I understand ELF correctly, then having multiple .so's is bad for > another reason. The more instructions a library contains that don't > refer to places relative to wherever the library got mapped, but to > other, lower level libraries, the more instructions need fixing up at > run time using the mapped addresses of /other/ libraries, because they > may be at different places for different applications. Which is precisely what prelinking fixes (if i understand you correctly). > And each time a page of code in a library contains instructions that > must be fixed up at load time for an application, that page cannot be > shared among applications. A waste of memory. This i believe is incorrect, one a library is in memory, all binaries that are loaded that use it have their symbols mapped to the library in memory. I dont know too many of the details of how linux does this so i might be mistaken. Tom
Attachment:
pgpL96OQUoLhW.pgp
Description: signature