Timeline for non-reentrant libraries in shared memory?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2016 at 14:41 | comment | added | user732 | @RuiFRibeiro - It is said that one of the advantages of dynamic libraries is code sharing. The way ELF shared objects work, the kernel can do that. The "RE" LOAD header parts can be shared all over. It should also be possible to map the global variables (the "R W" LOAD header) as copy-on-write, so that as long as some process has it mapped, the kernel can just set up a mapping, vs reading it in from disk. So even the globals can be shared in a way. | |
| Mar 12, 2016 at 8:48 | comment | added | Rui F Ribeiro | That´s quite a nice post about executable files. I got lost in your explanation of libc.so in the paragraph before the last. Is not one of the advantages of dynamic libraries for one copy be shared among all processes using it at a time? | |
| Mar 11, 2016 at 16:06 | vote | accept | enigmaticPhysicist | ||
| Mar 11, 2016 at 14:30 | history | answered | user732 | CC BY-SA 3.0 |