On Mon, Feb 11, 2019 at 6:51 PM Waldek Kozaczuk <[email protected]> wrote:
> > I agree with you that messing at this level (loading/unloading elf) would > only complicate things more. Given that most expensive part is loading code > from the disk, maybe we could somehow optimize things at the lower level. > We would still unload object in terms of destructing how its is > represented, but we would not unmap() from memory and make it stay in > memory wherever the ELF file segments were loaded to. So that when the same > program (same path) gets loaded, we would still create it representation > state, run init functions, etc, but we would skip loading corresponding > file fragments from disk. > Doesn't this already happen even if you do unmap(), because ZFS (and I don't remember about ROFS) already has a cache for previously read disk blocks, and this doesn't get invalidated by an unmap()? -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
