[libfabric-users] OFI libfabric and forking
wzam at amazon.com
Wed Nov 24 14:27:45 PST 2021
I think for any provider that needs to pin memory during memory registration, using fork can cause data corruption, thus will cause problem.
The EFA provider registered a fork callback function to prevent user from using fork, unless they enable the additional fork support.
From: Libfabric-users <libfabric-users-bounces at lists.openfabrics.org> on behalf of Howard Pritchard <hppritcha at gmail.com>
Date: Wednesday, November 24, 2021 at 1:47 PM
To: "libfabric-users at lists.openfabrics.org" <libfabric-users at lists.openfabrics.org>
Subject: [EXTERNAL] [libfabric-users] OFI libfabric and forking
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Before I open an issue against libfabric, I've got a high level question.
If an application process initializes libfabric, and in particular, uses the memory monitor infrastructure, should the application be able to fork additional processes without problems?
Assume the forked processes are not utilizing libfabric in any way.
I just wanted to get a sanity check before opening an issue post Thanksgiving holidays.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libfabric-users