From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: [PATCH] libdmacm/rspreload: Avoid rsocket calls until after fork Date: Sun, 26 Aug 2012 10:25:53 +0300 Message-ID: <5039CF81.6010304@mellanox.com> References: <1828884A29C6694DAF28B7E6B8A8237346A8AB32@ORSMSX101.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237346A8AB32-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Hefty, Sean" Cc: "linux-rdma (linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)" , Yishai Hadas List-Id: linux-rdma@vger.kernel.org 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 ibv_fork_init or setting one of libibverb's yyy_FORK_SAFE env vars? Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html