public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: RDMA mailing list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma-core soon in Debian
Date: Fri, 14 Jul 2017 10:06:57 -0600	[thread overview]
Message-ID: <20170714160657.GC25760@obsidianresearch.com> (raw)
In-Reply-To: <1500041591.3563.31.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>

On Fri, Jul 14, 2017 at 04:13:11PM +0200, Benjamin Drung wrote:
> 3) Get rid of openibd and rdma service dependencies:
> 
> $ git grep openibd
> ibacm/CMakeLists.txt:set(rdmascript "openibd")
> srp_daemon/CMakeLists.txt:set(RDMA_SERVICE "openibd" CACHE STRING

I think Bart fixed most of these issues when he added systemd support,
so I recommend removing it from SRP for init.d as well.

No idea about what is wrong with ibacm that it needs this strange
ordering. Guessing we probably needs hotplug support in verbs to fully
make it work reliably, Yishia has patches for that pending..

Ideally we would make ibacm socket activate which will ameliorate most
boot time ordering issues even if there are still hot plug bugs in
ibacm..

Jason
--
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:[~2017-07-14 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 14:13 rdma-core soon in Debian Benjamin Drung
     [not found] ` <1500041591.3563.31.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-07-14 15:16   ` Leon Romanovsky
2017-07-14 16:06   ` Jason Gunthorpe [this message]
2017-07-27 22:37   ` Jason Gunthorpe

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=20170714160657.GC25760@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox