From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [ANNOUNCE] Shared Topic Branch For ABI Changes
Date: Thu, 21 Apr 2016 14:01:02 -0600 [thread overview]
Message-ID: <20160421200102.GB6258@obsidianresearch.com> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373AB04435E-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, Apr 21, 2016 at 06:17:18PM +0000, Hefty, Sean wrote:
> > Doug was ambivalent, Steve was against. There was a concern the natual
> > release schedual of the parts was different, so why link them.
> >
> > My counter was that isn't really important, the goal is is to reduce
> > developer time when working on this mess.
> >
> > Since we are looking at changing *everything* developer time seems
> > more important right now.
>
> FWIW, I moved the librdmacm and libibacm into a single guthub
> project. Even if we don't share a single git tree, this enables
> multiple maintainers for the code. I would really like to see
> libibcm dropped entirely, and think libibverbs and librdmacm should
> merge.
+1
> In the past I would have been in favor of more closely associating
> libibumad with libibverbs, but now that OPA uses IB-like management,
> I'm not so sure. I think OPA management could be done outside of
> any verbs emulation. Ira might know for sure.
IIRC OPA still uses /dev/umad. I suspect libmad/umad needs to grow new
structures and constants primarily.
I would call the combined repo 'rdma-plumbing' or something, intended
to cover the user space side for all the kernel interfaces.
I saw libfabric was having success with this model - is that accurate?
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
next prev parent reply other threads:[~2016-04-21 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 5:52 [ANNOUNCE] Shared Topic Branch For ABI Changes Leon Romanovsky
[not found] ` <20160420055221.GT6349-2ukJVAZIZ/Y@public.gmane.org>
2016-04-20 15:29 ` Jason Gunthorpe
[not found] ` <20160420152924.GA25424-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-04-21 6:58 ` Leon Romanovsky
[not found] ` <20160421065847.GC12730-2ukJVAZIZ/Y@public.gmane.org>
2016-04-21 17:38 ` Jason Gunthorpe
[not found] ` <20160421173815.GB5102-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-04-21 18:17 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB04435E-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-04-21 20:01 ` Jason Gunthorpe [this message]
[not found] ` <20160421200102.GB6258-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-04-21 20:29 ` Hefty, Sean
2016-04-21 6:49 ` Leon Romanovsky
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=20160421200102.GB6258@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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