3 ms·
Assuming their translation step is as cheap as they claim (single pass rewrite/substitute missing hardware for software macros), it's conceivable that there isn
by _wmd 13y ago
Assuming their translation step is as cheap as they claim (single pass rewrite/substitute missing hardware for software macros), it's conceivable that there isn't much value in persistently caching the result.
In that case, everything could be contained to a single ld.so patch, or (doubtfully) a modification to the kernel ELF loader
Finally, and although it is less common now, in prior days Linux already had a post-install processing step for binaries on certain distributions - prelink(8) ( https://en.wikipedia.org/wiki/Prelink https://en.wikipedia.org/wiki/Prelink )
- rst 13y agoAlso Mac OSX "prebinding" and (in later releases) dyld cacheing. Though just skipping the cache entirely is certainly the quickest way to get something running --- and quite a few plausible server workloads will pay the penalty mainly at startup, when it might not matter so much. (But yeah, keep it in user space, if only to make it easier to debug!)