From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@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 18:16:47 +0300 [thread overview]
Message-ID: <20170714151647.GC1528@mtr-leonro.local> (raw)
In-Reply-To: <1500041591.3563.31.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]
On Fri, Jul 14, 2017 at 04:13:11PM +0200, Benjamin Drung wrote:
> Hi everyone,
>
> a few weeks passed since my last status update regarding rdma-core in
> Debian. We made good progress in getting it ready. Only three items are
> left:
>
> 1) I sent three patches for the ibacm and iwpmd service to the mailing
> list. They need to be reviewed and accepted:
>
> $ git log --oneline master..bdrung
> c3654500 ibacm: Add systemd service file
> 562d5a00 iwpmd: Support Debian/Ubuntu in sysvinit service
> 9744e8d2 ibacm: Fix service start_daemon call on Debian
It will be merged on Sunday, depends on lack of objections.
>
> 2) Common infrastructure for auto loading rdma modules: See the "Add
> rdma service for kernel boot support" thread on this mailing list.
> Jason Gunthorpe made a very good proposal were I made some comments on
> it.
>
> 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
> "init.d file service name to order srpd after")
> $ git grep rdma.service -- ibacm/
> ibacm/ibacm.service.in:Requires=rdma.service
> ibacm/ibacm.service.in:After=rdma.service opensm.service
>
> openibd is not part of rdma-core and rdma.service will go away with the
> changes in point 2.
>
>
> I expect to see progress on these points in the coming days / next
> week. When all changes are in master, will we create a new release?
> Otherwise I will have to base my upload on v14 and cherry-pick all
> relevant changes.
Usually, we are releasing rdma-core, a week or two after Linus's -rc1
release. Let's see how the progress will be and decide then.
Thanks
>
> --
> Benjamin Drung
> System Developer
> Debian & Ubuntu Developer
>
> ProfitBricks GmbH
> Greifswalder Str. 207
> D - 10405 Berlin
>
> Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
> Web: https://www.profitbricks.com
>
> Sitz der Gesellschaft: Berlin.
> Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
> Geschäftsführer: Achim Weiss.
>
> --
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-14 15:16 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 [this message]
2017-07-14 16:06 ` Jason Gunthorpe
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=20170714151647.GC1528@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@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