From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 26257@debbugs.gnu.org
Subject: bug#26257: [PATCH] gnu: Add rdma-core.
Date: Mon, 27 Mar 2017 13:55:54 +0200 [thread overview]
Message-ID: <87fuhzj5md.fsf@gnu.org> (raw)
In-Reply-To: <20170325203353.15515-1-mbakke@fastmail.com> (Marius Bakke's message of "Sat, 25 Mar 2017 21:33:53 +0100")
Marius Bakke <mbakke@fastmail.com> skribis:
> * gnu/packages/linux.scm (rdma-core): New variable.
LGTM!
> + (home-page "https://github.com/linux-rdma/rdma-core")
> + (synopsis "Utilities and libraries for working with RDMA devices")
> + (description
> + "This package provides the userspace components for the InfiniBand
> +subsystem of the Linux kernel. Specifically it contains userspace libraries
> +for the following device nodes:
> +
> +@enumerate
> +@item @file{/dev/infiniband/uverbsX} (@code{libibverbs})
> +@item @file{/dev/infiniband/rdma_cm} (@code{librdmacm})
> +@item @file{/dev/infiniband/umadX} (@code{libibumad})
> +@end enumerate
> +
> +The following service daemons are also provided:
> +@enumerate
> +@item @code{srp_daemon} (for the @code{ib_srp} kernel module)
> +@item @code{iwpmd} (for iwarp kernel providers)
> +@item @code{ibacm} (for InfiniBand communication management assistant)
> +@end enumerate")
I was wondering whether this code was relying on proprietary InfiniBand
drivers, which would not be okay, but
find $LINUX_MODULE_DIRECTORY -name ib\*ko
shows a bunch of drivers, including ‘ib_srp’ (mentioned above), so I
guess this is fine.
Thanks!
Ludo’.
next parent reply other threads:[~2017-03-27 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170325203353.15515-1-mbakke@fastmail.com>
2017-03-27 11:55 ` Ludovic Courtès [this message]
2017-03-28 15:08 ` bug#26257: [PATCH] gnu: Add rdma-core Marius Bakke
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=87fuhzj5md.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26257@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.