[openib-general] Re: Re: Re: madvise MADV_DONTFORK/MADV_DOFORK

[Michael S. Tsirkin]

Quoting Roland Dreier <rdreier at cisco.com>:
>     Gleb> Roland can you please tell the history behind memory.c?
> 
> This was used for mlock() when that was required.  The reason I left
> it around was that I always thought that the MADV_DONTFORK would be
> handled the same way.
> 
> Probably the best thing to do would be to have libibverbs handle the
> madvise() stuff transparently by default, but perhaps add some hooks
> for more intelligent applications or MPI libraries to do their own thing.

How would the hook look like?

-- 
Michael S. Tsirkin
Staff Engineer, Mellanox Technologies