> > rsockets enables fork support only when RDMAV_FORK_SAFE has been set.
> > I do not call ibv_fork_init().
>
> understood, so you see the problem also when RDMAV_FORK_SAFE has been set?
yes
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majo
On Mon, Aug 27, 2012 at 8:54 PM, Hefty, Sean wrote:
> rsockets enables fork support only when RDMAV_FORK_SAFE has been set.
> I do not call ibv_fork_init().
understood, so you see the problem also when RDMAV_FORK_SAFE has been set?
Or.
--
To unsubscribe from this list: send the line "unsubscrib
> Are you calling from rsockets to ibv_fork_init or setting one of
> libibverb's yyy_FORK_SAFE env vars?
rsockets enables fork support only when RDMAV_FORK_SAFE has been set. I do not
call ibv_fork_init().
- Sean
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the
On 23/08/2012 21:51, Hefty, Sean wrote:
It's not clear what the specific problem is. The best guess is
that libibverbs or the provider library (e.g. libmlx4) perform
some initialization, such as mmap'ing device memory, which does not
work when fork is called.
Are you calling from rsockets to i
On 23/08/2012 21:51, Hefty, Sean wrote:
When an rsocket call is made before an application calls fork(),
the forked applications can hang. This can be seen by running
netserver and two netperf clients simultaneously. The second
netperf client will eventually stop performing data transfers.
LD_
