From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Infiniband/OmniPath/iWARP and other RDMA related staff
Date: Wed, 29 Jun 2016 13:19:06 +0000 (UTC) [thread overview]
Message-ID: <pan$17a5d$363781e2$aae7d1fa$d59573da@applied-asynchrony.com> (raw)
In-Reply-To: 1683311.HyPf7WlIoB@x240
On Wed, 29 Jun 2016 10:07:07 +0300, Alexey Shvetsov wrote:
> Hi all!
>
> I'm going to revive RDMA fabric related things in gentoo. And since its not
Yay!
> only about infiniband staff but about more generic fabric types there is and
> idea to rename category sys-infiniband to more generic name. Suggestions are
>
> sys-rdma
> sys-fabric
>
> What will be inside? It will be RDMA related stuff like OFED, fabric userspace
> drivers (verbs, psm, psm2, libfabric and others), plugins for specific devices,
> tools to flash RDMA cards and other related staff.
This makes me happy. I've been playing with a standalone libfabric in my
overlay via the sockets/UDP providers, and had nothing but problems when I
tried to add USE flags for the various OFED bits (psm2 etc.)
An up-to-date libfabric that pulls in ofed only when needed would finally enable
people without the otherwise necessary fabric HW to write against the much more
usable & sane (when compared to raw IB verbs) libfabric APIs.
As far as the name is concerned IMHO fabric sounds less RDMA-specific;
I think the OFI WG now also prefers implementation-neutral terms.
cheers,
Holger
next prev parent reply other threads:[~2016-06-29 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 7:07 [gentoo-dev] Infiniband/OmniPath/iWARP and other RDMA related staff Alexey Shvetsov
2016-06-29 7:26 ` Andrew Savchenko
2016-06-29 11:34 ` Aaron Bauman
2016-06-29 13:19 ` Holger Hoffstätte [this message]
2016-06-29 13:46 ` [gentoo-dev] " Alexey Shvetsov
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='pan$17a5d$363781e2$aae7d1fa$d59573da@applied-asynchrony.com' \
--to=holger@applied-asynchrony.com \
--cc=gentoo-dev@lists.gentoo.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