Dllicious – shared object usage analysis on Linux

Re:Dllicious – shared object usage analysis on Linux by azalemeth on Sunday February 06, 2022 @05:18AM (#30231113)

> You would need two distinct, long-lived dynamically-linked executables, both being hot at the same time, and both having libc (or another common library) in the hotpath at the same time.

Like, for example, bash and a process you are executing in parallel in a loop?

[ Parent | on HN ]

Re:Dllicious – shared object usage analysis on Linux by 5a04fcd55b8 on Sunday February 06, 2022 @07:47AM (#30232040)

I may be missing something... Is bash exec()ing something in the loop? If so, caches will be the least of our concerns; there will be context switches, system calls, and even I/O, all orders of magnitude slower than even DRAM access. Otherwise, what is bash doing in the loop? When is bash ever CPU-bound?... in a library function call... that is also called by the other process?

[ Parent | on HN ]