Shared Topic Branch For ABI Changes
Hi,
Following the discussions at OFVWG (4/19/2016), I want to present shared repository and topic branch for ABI change proposed patches.
Please post them on linux-rdma mailing list with clear indication that it is supposed for ABI related work.
I would like to suggest to use [PATCH ABI xxx] notation, so it will be easy for me to take them and don't mix with general RDMA development.
Kernel part git address:
* git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
* https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/
Branch name:
* topic/abi
The supplementary user space (libibverbs) repository will be set a little bit later.
Thanks
A message that is not in the archive (sent off-list or not yet received): 20160420055221.GT6349-2ukJVAZIZ/[email protected]
Quoted 2 lines · Leon Romanovsky
The supplementary user space (libibverbs) repository will be set a little bit later.
We should also re-consider the idea that has been floated a few times over the years:
Combine all the RMDA plumbing libraries into one git repository.
This is librdmacm, libibverbs, libucm, libumad, libmad, libmlx4/5/mtcha/ipath/cxgb/etc/etc
With the scope of the planned work this would seem essential to me.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20160420152924.GA25424-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org
Quoted 5 lines · Jason Gunthorpe
Quoted 2 lines · Leon Romanovsky
The supplementary user space (libibverbs) repository will be set a little bit later.
Quoted 7 lines
We should also re-consider the idea that has been floated a few times over the years:
Combine all the RMDA plumbing libraries into one git repository.
This is librdmacm, libibverbs, libucm, libumad, libmad, libmlx4/5/mtcha/ipath/cxgb/etc/etc
Can you point me to relevant discussion?
Thanks.
A message that is not in the archive (sent off-list or not yet received): 20160421065847.GC12730-2ukJVAZIZ/[email protected]
Quoted 9 lines · Leon Romanovsky
Quoted 8 lines · Jason Gunthorpe
Quoted 2 lines · Leon Romanovsky
The supplementary user space (libibverbs) repository will be set a little bit later.
We should also re-consider the idea that has been floated a few times over the years:
Quoted 6 lines
Quoted 4 lines
Combine all the RMDA plumbing libraries into one git repository.
This is librdmacm, libibverbs, libucm, libumad, libmad, libmlx4/5/mtcha/ipath/cxgb/etc/etc
Can you point me to relevant discussion?
I couldn't find it in the archive quickly. Doug, myself and Steve Wise were talking about it after Doug started.
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.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20160421173815.GB5102-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org
Quoted 8 lines
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.
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.
- Sean
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 1828884A29C6694DAF28B7E6B8A82373AB04435E-P5GAC/[email protected]
Quoted 6 lines · Sean
Quoted 6 lines
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.
Quoted 8 lines
Quoted 2 lines
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
Quoted 4 lines
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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 20160421200102.GB6258-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org
Quoted 4 lines
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?
Libfabric integrated the provider code directly into the same repo. I would say that that model is working well. It's allowing greater code sharing and makes it much easier to test multiple providers. So I would say there's significant benefits for merging. --
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 15 lines · Leon Romanovsky
Hi,
Following the discussions at OFVWG (4/19/2016), I want to present shared repository and topic branch for ABI change proposed patches.
Please post them on linux-rdma mailing list with clear indication that it is supposed for ABI related work.
I would like to suggest to use [PATCH ABI xxx] notation, so it will be easy for me to take them and don't mix with general RDMA development.
Kernel part git address:
*git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
* https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/
Quoted 5 lines
Branch name:
* topic/abiThe supplementary user space (libibverbs) repository will be set a little bit later.
Libibverbs:
* git://git.kernel.org/pub/scm/libs/leon/libibverbs.git
* https://git.kernel.org/cgit/libs/leon/libibverbs.git/
Branch name:
* topic/abi
Quoted 2 lines
Thanks