All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma
	(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] libdmacm/rspreload: Avoid rsocket calls until after fork
Date: Sun, 26 Aug 2012 10:25:53 +0300	[thread overview]
Message-ID: <5039CF81.6010304@mellanox.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237346A8AB32-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.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

  parent reply	other threads:[~2012-08-26  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 18:51 [PATCH] libdmacm/rspreload: Avoid rsocket calls until after fork Hefty, Sean
     [not found] ` <1828884A29C6694DAF28B7E6B8A8237346A8AB32-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-26  4:20   ` Or Gerlitz
2012-08-26  7:25   ` Or Gerlitz [this message]
     [not found]     ` <5039CF81.6010304-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2012-08-27 17:54       ` Hefty, Sean
     [not found]         ` <1828884A29C6694DAF28B7E6B8A8237346A8B2E4-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-08-27 21:34           ` Or Gerlitz
     [not found]             ` <CAJZOPZKXBt01QfQOd-vd_-MGnycjxexDmfpGbpvrV7SZf_eRAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-27 22:13               ` Hefty, Sean

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5039CF81.6010304@mellanox.com \
    --to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.