News for hackers. Stuff that matters.
Re:The C standard library function atexit is broken by mikeash on Wednesday June 19, 2019 @10:17PM (#20229258)
A typical system has dozens or hundreds of processes running even when nothing is going on. If they all had their own copy of every system library in RAM, it wouldn’t look so free. Especially on mobile devices.
Re:The C standard library function atexit is broken by zingermc on Wednesday June 19, 2019 @10:26PM (#20229296)
What if the OS could dedupe pages?
Re:The C standard library function atexit is broken by adrianmonk on Thursday June 20, 2019 @01:21AM (#20230129)
You'd need to arrange for the linking process to result in identical (and identically-aligned!) code pages. If you're going to all the trouble to ensure that, why not just write it all to a file and call it a shared library?
Re:The C standard library function atexit is broken by bayareanative on Thursday June 20, 2019 @06:08AM (#20231358)
Exactly. Emperors' new clothes from naive convention abandonment of solved problems.
Re:The C standard library function atexit is broken by loeg on Thursday June 20, 2019 @01:00AM (#20230029)
On the fly memory dedupe is incredibly expensive. Especially compared to just not duplicating in the first place.

Also, it's quite likely that static linked libraries wouldn't be located at the exact same page offsets every time they're linked in to a binary, making page-level dedupe not useful.

Re:The C standard library function atexit is broken by sebcat on Thursday June 20, 2019 @01:38AM (#20230207)
What if the OS could map a shared object that resides in one section of memory into the virtual address space of multiple processes?
Re:The C standard library function atexit is broken by kelnos on Wednesday June 19, 2019 @11:28PM (#20229593)
Do any OSes actually do this, though? If not, this is academic until one actually does.

Linux does have something called "KSM" that de-dupes memory pages, but it appears that it's only so a hypervisor can de-dupe guest OS pages? Odd that it's not more general than that. Though I guess there is a cost: the KSM code needs to scan through memory to find duplicate pages, which I can't imagine is fast.

Re:The C standard library function atexit is broken by choeger on Thursday June 20, 2019 @04:06AM (#20230860)
Would not work with any kind of LTO.
Re:The C standard library function atexit is broken by CamperBob2 on Wednesday June 19, 2019 @10:30PM (#20229309)
Meh, not so much. The processes will only page in the code they actually use.

Shared libraries are a goofy hack dating back to a time when people mistakenly thought they needed them, and they need to go away.

Re:The C standard library function atexit is broken by Annatar on Thursday June 20, 2019 @01:51AM (#20230267)
Shared object libraries are incredibly useful because they save memory and CPU resources. Cloning the process space during a fork(2) call, initializing structures, then context switching and whatnot is incredibly expensive.
Re:The C standard library function atexit is broken by _rtld_global_ro on Thursday June 20, 2019 @10:32AM (#20233278)
shared library can be expensive as well, the dynamic symbol lookup could be a lot more expensive than people would assume.
Re:The C standard library function atexit is broken by notacoward on Thursday June 20, 2019 @08:07PM (#20238721)
Correct. Shared libraries trade away CPU for memory. Even with some benefits in terms of cache warmth, the extra indirection and loader/VM complexity make shared libraries a net loss in terms of CPU.
Re:The C standard library function atexit is broken by coldtea on Thursday June 20, 2019 @04:05AM (#20230856)
>Cloning the process space during a fork(2) call, initializing structures, then context switching and whatnot is incredibly expensive.

Err, we're running Electron apps today, with a full blown embedded browser engine, a vm, and a hellish complex DOM for rendering. Others run apps inside containers, with their own basic OS and standard libs -- compared to that the above is negligible.

Re:The C standard library function atexit is broken by saagarjha on Thursday June 20, 2019 @04:47AM (#20231037)
> we're running Electron apps today

Some of us try not to on the belief that they don't perform acceptably.

Re:The C standard library function atexit is broken by imtringued on Thursday June 20, 2019 @07:42AM (#20231821)
You can usually avoid this problem by using the web version of Slack, Discord, Rocketchat, etc. A single browser running everything is obviously more efficient than running ten.
Re:The C standard library function atexit is broken by bayareanative on Thursday June 20, 2019 @06:12AM (#20231374)
Nope. A strawman wrong doesn't justify anything related to the topic. fork() duplicates everything, which maybe overkill, which is why pthreads and vfork+exec also exist.
Re:The C standard library function atexit is broken by notacoward on Thursday June 20, 2019 @08:04PM (#20238708)
That's not why pthreads exist, and vfork barely does. Pthreads exist to facilitate parallel operation (hence the name) on shared data, not as an efficiency measure. As for vfork, it has been deprecated since every UNIX implementation started marking pages as copy-on-write instead of actually copying. I was doing some of that work myself in 1990-91, so it's hardly new.

The real problems with static linking don't have to do with fork, except in the sense of increasing reliance on VM overcommit (which IMO is a bad idea already). It's more to do with masking reuse of the same library across unrelated processes, as an efficiency issue but even more importantly in terms of tracking dependencies and updating software. No matter how good your configuration management (or similar mechanism) is, rebuilding large-N statically linked executables is less efficient and more error-prone than using the same information to update small-N shared libraries.