[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Shared libs without MMU resources
I hope you won't mind that I reply to the list.
Standa Opichal wrote:
Thanks for the clarifications. Could you, please review the following?
4) .so libs without real sharing (any working gcc target, anyhow
gcc has nothing to do with that. It is the linker, ld, that would
produce the shared libraries (.so).
Would need to provide the relocation tables to be appended to the
generated .o/.so/binary files. OS would not feature any sharing, but just
load the whole thing into memory each time is is requested to be linked
together and relocate to a particular physical address (no VM).
I think this is a very good idea.
Would this be really enormous piece of work?
It shouldn't be that much work.
Your idea is to provide dynamic linking, but still keep a private copy
of the entire code (text and data) in each processes memory, correct?
Of course, you will not save any memory if you copy the code, but you
will still have a lot of advantages. Not only, that you save a lot of
recompilation and repackaging after changing a shared library; a lot of
software that links modules/plug-ins dynamically (Apache, Perl, ...)
would become a lot more usable.
Imperia AG, Development
Leyboldstr. 10 - D-50354 Hürth - http://www.imperia.net/